Hi Volker
you wrote:
At 12:41 PM 4/6/00 +0200, you wrote:
>>> parse "LIB1 " ["LIB1"]
>== false
>>> parse "LIB1 " ["LIB1" to end]
>== true
>>> parse "LI B1 " ["LIB1" to end]
>== false
>
>result says, could parse full string, or there is a rest, IMO.
that
>> parse "LIB1 " ["LIB1"]
== false
>> parse "LIB1 " ["LIB1" to end]
== true
>> parse "LI B1 " ["LIB1" to end]
== false
result says, could parse full string, or there is a rest, IMO.
Volker
Am Mit, 05 Apr 2000 schrieben Si
Hi bciceron,
The short version is: I believe it's a bug.
The long version:
space at the begining of string:
>> parse " LIB1" ["LIB1"]
== true
space smack in the middle of token:
>> parse "LI B1" ["LIB1"]
== false
Now, that somehow makes sense. If I am parsing for the token LIB1 I do not
wa
--Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 05, 2000 10:42 AM
To: [EMAIL PROTECTED]
Subject: [REBOL] parse / space
parse is very powerfull but still kills me with spacer:
>> parse "asergd" lib-name
== true
>> parse &qu
parse is very powerfull but still kills me with spacer:
>> parse "asergd" lib-name
== true
>> parse "LIB1" lib-type
== true
so the 2 elements matches the 2 single rules.
but pout together they don't :
>> parse "asergd LIB1" [lib-name lib-type]
== false
>> probe parse "asergd LIB1" [lib-name
