When simply splitting a string including a "stand-alone" semi-colon, parse returned an empty block at the position of the semi-colon. It doesn't do this when it encounters a "stand-alone" tab or newline. >> parse "this string includes a semi-colon ; <-there" none == ["this" "string" "includes" "a" "semi-colon" "" "<-there"] >> parse "this string includes a newline ^/ <-there" none == ["this" "string" "includes" "a" "newline" "<-there"] >> parse "this string includes a tab ^- <-there" none == ["this" "string" "includes" "a" "tab" "<-there"] Is this a bug or a feature? Personally I would prefer it if "parse string none" left semi-colons untouched. Regards Peter
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.15 - Release Date: 22/05/2005 -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
