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
Apparently the 'some is matching the leading/trailing white space:
>> parse " LIB1 " [lib-type]
== false
>> parse " LIB1 " [some lib-type]
== true
Curiously though, try this:
>> parse "asergd asergd" [some symbol some symbol]
== false
>> parse "asergd asergd" [some symbol]
== true
Thus, [some
