----- Original Message -----
From: "Mat Bettinson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 19, 2001 4:26 PM
Subject: [REBOL] Re: Parse doing weird things...


> Heya Mat,
>
> MB> All of the above leads me to think there is some sort of restriction
> MB> to how much data can be parsed before some sort of
> MB> feature/limitation/bug is run into.
>
> So I tried to fix this myself;
>
> >> parse copy/part find tmp/content "Etymology:" 256 [thru "Etymology:"
copy DictEnty to "<br>"]
> == false
>
> The above line should limit the parsing to a 256 character length
> string starting from exactly where we were going to 'thru' to anyhow.
> It *still* doesn't work.
>
> I mean look for yourself!
>
> >> print copy/part find tmp/content "Etymology:" 256
> Etymology:
Portuguese<i>pe&atilde;o</i>&amp;French<i>pion,</i>fromMedievalLatin<i>pedon
-,pedo</i>footsoldier--moreat<ahref="dicti
> onary?book=Dictionary&va=pawn"><fontsize="-1">PAWN</font></a><br>Date:
1609<br><b>1</b><b>:</b>anyofvariousworkersinIndia,SriLa
> >>
>
> There's the Etymology: and there's the goddamn <br>! Why the hell
> doesn't it work?! Argh!

seems to work here....

->> parse str [thru "Etymology:" copy DictEntry to "<br>" to end]
== true
->> print dictentry

Portuguese<i>pe&atilde;o</i>&amp;French<i>pion,</i>fromMedievalLatin<i>pedon
-,pedo</i>footsoldier--moreat<ahref="dicti
onary?book=Dictionary&va=pawn"><fontsize="-1">PAWN</font></a>
->>

maybe you could try to use parse/all to take speces into account ....

Cheers,
-pekr-

> --
> Mat Bettinson - EuroGamer's Gaming Evangelist with a Goatee
> http://www.eurogamer.net | http://www.eurogamer-network.com
>
>
> --
> To unsubscribe from this list, please send an email to
> [EMAIL PROTECTED] with "unsubscribe" in the
> subject, without the quotes.

-- 
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the 
subject, without the quotes.

Reply via email to