public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: leonp@plris.com
To: Mo DeJong <mdejong@cygnus.com>
Cc: sourcenav@sourceware.cygnus.com
Subject: Re: SN Doesn't recognize bool true/false
Date: Mon, 09 Apr 2001 08:19:00 -0000	[thread overview]
Message-ID: <5.0.2.1.0.20010409171926.00a9be88@plris.com> (raw)
In-Reply-To: <Pine.SOL.3.91.1010405230339.29851L-100000@cse.cygnus.com>

At 23:05 05/04/01 -0700, you wrote:
>On Wed, 4 Apr 2001 leonp@plris.com wrote:
>
> > Hello, all.
> >          Does anybody know the cause that SN C-parser doesn't recognize
> > "false" and "true" words (while do recognize "bool")?
> > Thanks.
>
>Because it has not been implemented. Seriously, adding
>support for this kind of thing is not hard at all,
>someone just needs to sit down for 20 minutes and
>actually do it.
>
>Why don't you try this patch out and see if it works for you?
>
>Index: c_high.l
>===================================================================
>RCS file: /cvs/cvsfiles/devo/snavigator/hyper/c_high.l,v
>retrieving revision 1.12
>diff -u -r1.12 c_high.l
>--- c_high.l    2001/02/26 00:48:08     1.12
>+++ c_high.l    2001/04/06 06:03:26
>@@ -145,6 +145,7 @@
>  else |
>  enum |
>  extern |
>+false |
>  float |
>  for |
>  friend |
>@@ -174,6 +175,7 @@
>  template |
>  this |
>  throw |
>+true |
>  try |
>  typedef |
>  union |
>
>Mo DeJong
>Red Hat Inc

I apologize for not to be able to test this yet - I still didn't forced 
myself to study the Windows installation of SN from sources - it was 
written somewhere several times, that it is a real pain (as all the Windows 
is).

Yet, the patch seems to work, I did the debugging by my eyes. :-))


Leon Pollak
leonp@plris.com

      reply	other threads:[~2001-04-09  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04  6:51 leonp
2001-04-04 11:38 ` D-Man
2001-04-05 23:05 ` Mo DeJong
2001-04-09  8:19   ` leonp [this message]

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=5.0.2.1.0.20010409171926.00a9be88@plris.com \
    --to=leonp@plris.com \
    --cc=mdejong@cygnus.com \
    --cc=sourcenav@sourceware.cygnus.com \
    /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).