public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ediaz@veridis.com
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/9689: Number: 9688 update : pasting "<" and "ValidStruct" does not give a valid preprocessing token
Date: Thu, 13 Feb 2003 10:06:00 -0000	[thread overview]
Message-ID: <20030213100014.27669.qmail@sources.redhat.com> (raw)


>Number:         9689
>Category:       preprocessor
>Synopsis:       Number: 9688 update : pasting "<" and "ValidStruct" does not give a valid preprocessing token
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Thu Feb 13 10:06:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     ediaz@veridis.com
>Release:        g++ (GCC) 3.3 20030212 (prerelease)
>Organization:
>Environment:
SuSE 7.3/Linux
>Description:
c&p of the #9688 descripton :

When I try to compile a file using macros of templates, I get a 'MyFileStruct.h:541:67: pasting "<" and "MyStruct" does not give a valid preprocessing token' message.

It worked perfectly with the 2.95.x serie and with the 3.2.1 version.

I've tryied to do it in two passes, with a --save-temps and a  g++ thefile.ii -c and it worked.  Like if the processed code was not the same as the preprocessor's output.

-----------

I've made a better & cleaner example and attached it :
>How-To-Repeat:
Explanations in test2.cpp
>Fix:
Use the two passes trick.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="test2.cpp"
Content-Disposition: inline; filename="test2.cpp"

/*

This is a better example of the problem (cleaner too)

How to fail :

sh-2.05$ g++ test2.cpp -o test2_fail
test2.cpp:46:11: pasting "<" and "Field" does not give a valid preprocessing token

How to success :

sh-2.05$ g++ test2.cpp --save-temps
test2.cpp:46:11: pasting "<" and "Field" does not give a valid preprocessing token
sh-2.05$ g++ test2.ii -o test2_success           
sh-2.05$

I hope it will helps.

Regards,

Eric Diaz

*/

#include<stdlib.h>
#include<stdio.h>
#include<string.h>

template <class T>
class C
 {
  T hold;
  
  public:
   
    C(T to_hold)
     {
      hold=to_hold;
     }
    
    static void process(T a_value)
     {
      puts("Generic");
      
      return 0;
     }
 };

#define CM(x)														\
template<>														\
class C < ##x >														\
{															\
public:															\
	static void process(x a_value)											\
	{														\
	 puts("Not Generic (" #x ")");											\
	}														\
};

struct Field
{
};

struct Field2
{
};

// The following will fail :

CM( Field )

// The following, being a copy&paste of the .ii output for the CM( Field )  (with Field replaced by Field2) will work.

template<> class C < Field2 > { public: static void process(Field2 a_value) { puts("Not Generic (" "Field2" ")"); } };

int main(int argc,char* argv[])
 {
  Field f1;
  Field2 f2;

  C<Field>::process(f1);
  C<Field2>::process(f2);
 
  return 0;
 }


             reply	other threads:[~2003-02-13 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 10:06 ediaz [this message]
2003-02-13 10:12 neil
2003-02-13 17:06 Zack Weinberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030213100014.27669.qmail@sources.redhat.com \
    --to=ediaz@veridis.com \
    --cc=gcc-gnats@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).