T.R | Title | User | Personal Name | Date | Lines |
---|
878.1 | | TLE::LUCIA | http://asaab.zko.dec.com/~lucia/biography.html | Tue Mar 11 1997 13:52 | 5 |
| Such is the way of the yacc-generated parser. "state" is a reserved word in the
ladebug grammar. Same with "print print" or "print thread" -- expressions which
are also ladebug reserved words must be enclosed in ().
Tim
|
878.2 | Mmmmm... | GALVIA::STONES | Tom Stones | Wed Mar 12 1997 08:32 | 5 |
| Mmmm - Yes I can see how a yacc grammar might cause it, but surely it is still a
bug. (a) It's a pain in the ... for the ladebug user and (b) the expression I
used is a legal C++ expression, so the error message indicates you have a
problem:
"Unable to parse input as legal command or C++ expression."
|
878.3 | | TLE::LUCIA | http://asaab.zko.dec.com/~lucia/biography.html | Wed Mar 12 1997 14:30 | 11 |
| A bug is behavior other than what is claimed. While we agree it is a pain, it
is the claimed and intended behavior. Significant work was done to investigate
this some time ago. I do not believe there are any current plans to revisit
this. At the time, you could not get ladebug to print variable named 'state' or
a Fortran variable named 'int'. Now, you can print (state) or print INT and it
will work just fine.
"Noted".
Tim
|
878.4 | | TLE::LUCIA | http://asaab.zko.dec.com/~lucia/biography.html | Thu Mar 13 1997 09:30 | 4 |
| Wanfang has pointed out the error of my thinking. Apparently, this is on the
list to be re-opened. I apologize for being uninformed.
Tim
|