RE: [cdt-dev] workaround available for 24030? (namespace/dtor par se ha

["Schaefer, Doug" <dschaefer@xxxxxxxxxxxx>]

Never mind, I just looked at it.  There seems to be problem in the error
recovery code of the parser.  It didn't progress to the next token when it
ran into the tilde in the destructor and just kept seeing the same error
over and over again.  I'm not sure why the hang didn't happen all the time
but I didn't study it too deeply.

Alain, can you forward me the bug and I'll submit a fix.

Cheers,
Doug Schaefer
Senior Staff Software Engineer
Rational - the software development company
Ottawa (Kanata), Ontario, Canada
 

-----Original Message-----
From: Schaefer, Doug [mailto:dschaefer@xxxxxxxxxxxx] 
Sent: Tuesday, February 04, 2003 10:01 PM
To: 'cdt-dev@xxxxxxxxxxx'
Subject: RE: [cdt-dev] workaround available for 24030? (namespace/dtor par
se hang)

The bad answer is that we are rewriting the parser and it should then be
able to handle this fairly simple file.  Unfortunately, we're a few weeks
before it is ready to hit the mainstream.  I would be curious why it was
hanging and try to put together a quick workaround.  If no one else has the
time, I can try and take a look at it next week.

Doug Schaefer
Senior Staff Software Engineer
Rational - the software development company
Ottawa (Kanata), Ontario, Canada
 

-----Original Message-----
From: Chris Schleicher [mailto:chrissch@xxxxxxxxxxxxxxxxxxx] 
Sent: Tuesday, February 04, 2003 6:09 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] workaround available for 24030? (namespace/dtor parse
hang)

I seem to have stumbled into 24030 and, as far as I can tell, there's
been barely any discussion of this bug on this (or any other) list.
A quick summary:  files with contents such as:

  namespace Foo {
    class Bar {
      public:
        Bar();
        ~Bar();
    };
  }

appear to hang Eclipse when attempting to open them with the C editor.
This is essentially all the info (i.e., no further activity) in the
bug DB. Has anyone looked into this? Any trivial workarounds?

What's particularly puzzling is that I have several files using this
paradigm which Eclipse happily digests -- suggesting there is some
way to get the JavaCC (?) parser to grok this syntax.

I'm using Eclipse 2.0.2 with the Jan 27th nightly CDT build.

Chris Schleicher

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev