From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: *
X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID,
	MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,323cf9d74a4ce4ed
X-Google-Attributes: gid103376,public
From: Ted Dennison <dennison@telepath.com>
Subject: Re: help on Ada project
Date: 1999/12/01
Message-ID: <823c66$d5q$1@nnrp1.deja.com>#1/1
X-Deja-AN: 555219055
References: <82204n$f3n$1@nnrp1.deja.com>
X-Http-Proxy: 1.0 x32.deja.com:80 (Squid/1.1.22) for client 204.48.27.130
Organization: Deja.com - Before you buy.
X-Article-Creation-Date: Wed Dec 01 14:43:26 1999 GMT
X-MyDeja-Info: XMYDJUIDtedennison
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.6 [en] (WinNT; I)
Date: 1999-12-01T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <82204n$f3n$1@nnrp1.deja.com>,
  phantom119@my-deja.com wrote:

> it's giving us some problems on string comparison,
> we are using a case statement to compare strings,

I suspect you are having trouble becuase you are trying to use a string
in a case statement. Case statements can only be used on discrete types,
not compound types like strings, arrays, or records. To get the same
effect on a string, you would need to use an "if...elsif...elsif.."
construct.

Another possibility would be to use nested case statements on individual
characters in the string. That would probably make for a faster lexer,
but its a lot more work.

--
T.E.D.


Sent via Deja.com http://www.deja.com/
Before you buy.