220 14112 <696e1057-69f4-40da-a50b-7251be4b970b@isocpp.org> article Path: news.gmane.org!not-for-mail From: Christopher Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: #pragma once Date: Tue, 21 Oct 2014 21:48:53 -0700 (PDT) Lines: 56 Approved: news@gmane.org Message-ID: <696e1057-69f4-40da-a50b-7251be4b970b@isocpp.org> References: <3d0ab5b0-73d9-434a-9ae4-cd47d8275590@isocpp.org> <59ae3383-67a5-4a4c-b301-06cf148c9df6@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5171_360901482.1413953333975" X-Trace: ger.gmane.org 1413953343 13541 80.91.229.3 (22 Oct 2014 04:49:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 22 Oct 2014 04:49:03 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCHINCHEQEFBBNXOTSRAKGQEF4R5RJA@isocpp.org Wed Oct 22 06:48:56 2014 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-ie0-f198.google.com ([209.85.223.198]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xgnqx-0007jU-PL for gclcip-std-proposals@m.gmane.org; Wed, 22 Oct 2014 06:48:55 +0200 Original-Received: by mail-ie0-f198.google.com with SMTP id tr6sf3070066ieb.9 for ; Tue, 21 Oct 2014 21:48:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe :content-type; bh=uUBoDKDuzp4+T/RUglAPm5E55sfIC2QoopDjUlNwYFc=; b=QH37nhVzpX8ztRzLdIvAexoqNKNXh+AJtomZxweW0wzvazC0RUCf4G8t7HLTlqtrFm KD3a83H5IWj/IXpGtxo2GOk470A92JMu+vfYBnqv4ZSbZWZRjftmtIV54xF7wGtKsC0P sxfEGFqWLGieW9bjiCT0/2rwVBIUnhBxtQmYdUguq01CEc92+ioh4ktHh/GuNYJpJzpC GhTIYf2VC64/TJLbzNip2J8xRIipK71P93Z0Ki7aEqMP6YqINjKclBVpMsTM4rPal8pY gilZYGR4dq2sysJxEfpakgQ7aeQqk5gBxXeKyTwsPfJR0Gdd346CDx1B0ebXM4w9Rky8 /v5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version:x-original-sender:reply-to:precedence :mailing-list:list-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=uUBoDKDuzp4+T/RUglAPm5E55sfIC2QoopDjUlNwYFc=; b=YAc/uL9EdnXrJsR57jhycOYkGvS3EzwC5m14jjalz8gSOCbLHhT6wo45jNmCNmAgDR oTmp03K4KPS0QkLcxEnGq4HM4Wigr4Jp7OkO1r+g1apVxZtbuzXA2H/7xJhok4OIoVHE n+7ZGktiWP/HAgXq5gAPVEujPsI9+eYEZ3rEMaw61vbLpQtfUYZwyT8TtUkvyDL02hmb 7fJNSzQx7aE1mI0fy3rpkbo40mQ2I29LZYbGH6AgD1NorqT25WTv9aYsy9rsmWO832SG gAgpLEGin67ISFcEKIX8o+s1qqpgHmzUAKtyVBgk4hXXqKFXIXf1xW/VEIH1rPb4Kset KYQQ== X-Gm-Message-State: ALoCoQkOJdNFCbY8+TxdRGiZpLfNOZRlWbZJlj+sgpHFj+7WxcAt9n9NYoOVEJ2U2G1+rtcXzR5v X-Received: by 10.42.110.66 with SMTP id o2mr2075593icp.11.1413953334909; Tue, 21 Oct 2014 21:48:54 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.140.41.74 with SMTP id y68ls581106qgy.15.gmail; Tue, 21 Oct 2014 21:48:54 -0700 (PDT) X-Received: by 10.140.82.75 with SMTP id g69mr13001qgd.9.1413953334304; Tue, 21 Oct 2014 21:48:54 -0700 (PDT) In-Reply-To: X-Original-Sender: christopherhallock@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:14112 Archived-At: ------=_Part_5171_360901482.1413953333975 Content-Type: text/plain; charset=UTF-8 > > Could we then define _Pragma as taking one or more string parameters (not > separated by anything but possibly whitespace) that are interpreted > concatenated? > I'm really curious about the original design intent: why does _Pragma take a stringized argument in the first place? When it was first added in C99, why wasn't it specified to take non-stringized tokens like the #pragma directive or MSVC's __pragma extension? -- --- You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/. ------=_Part_5171_360901482.1413953333975 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Could we then define _Pragma as taking one or more string paramete= rs (not separated by anything but possibly whitespace) that are interpreted= concatenated?

I'm really curious abou= t the original design intent: why does _Pragma take a stringized argument in the first plac= e? When it was first added in C99, why wasn't it specified to take non-stri= ngized tokens like the #pragma directive or MSVC's __pragma extension?

--

---
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposa= ls+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/<= /a>.
------=_Part_5171_360901482.1413953333975-- .