World: r3wp

But then this will give problem:
>> parse [1x2] [1x2]
== true

Yep.

But parse [1][1] ;== false (seems odd).

Maybe rebol needs a literal representation for ranges.

yes, but if you changed min/max to a pair, then
parse [1x2][1x2]
wourld fail.

I understand. I just suggesting that the parse dialect could be further 
optimized.

Or enhanced.

But I guess adding extra syntax still get us in trouble.

I guess block parsing is by datatypes and not Rebol values.

except for words .. hmm... confusing.

But numbers are literals when parsing. It's just that they're syntax 
too, at least in parse rules.

hi all, this is an "old" issue Graham: it is in REP for quite a long 
time

(together with my suggestion how to solve it)

where on REP ?

let me look

One place is this: http://www.compkarori.com/vanilla/display/TO%2C+THRU+And+NOT+PARSE+Rules
, but I think, there was more

then I found this: http://www.rebol.net/list/list-msgs/32392.html

LIT, or LITERAL would be good.

and one more: http://www.fm.vslib.cz/~ladislav/rebol/rep.html

how has Carl responded to these parse suggestions?

he said (a few days ago), that he will arrange for some uninterrupted 
time at the DevCon with me to hear my suggestions, so this is one 
more to remind him

Good.

good :-)

Ladislav - buy Carl some good whisky first ... better chance to succeed 
:-)

does he like whisky? I thought he loved REBOL wine?

hmm, I would have to find some old discussion with Carl, he likes 
whisky but he also suggested some othe drink to me :-)

Buy him some lousy wine so he will feel good that Sassenranch wine 
is so much better :)

:-) No problem with some bad czech wine :-)

buy him some 'burcak', he probably doesn't know, what it is ;)

I think he doesn't even know it is a drink

buy some copies of the sdk .. he won't worry about the wine then!

It will probably be hard to find bad wine, where the DevCon is in 
northern Italy. :-) And you're probably not allowed to bring bad 
wine into that area. ;-)

Any parse experts here today?

no matter...

Not an expert, but if you ask, you never know!!!

I want to split a text string at n characters but not in the middle 
of a word ie. split at the next space.

split-text: func [ txt n 
	/local frag result bl
][
    bl: copy []
    result: copy ""

    frag-rule: compose/deep [ copy frag (n) skip (print frag append result 
    frag) copy frag to #" " (if not none? frag [ print frag append result 
    frag ]
append bl copy result clear result) ]
    parse/all txt [ some frag-rule ]
    bl
]

works outside the function, but not inside :(

compose/deep [ copy frag (n) skip (print frag append result frag) 
copy frag to #" " (if not none? frag [ print frag append result frag 
]
append bl copy result clear result) ]


looks suspicious to me - don't forget that your parens are there 
for two different purposes. My guess is, that you don't need compose?

I think I tried it without the compose ...

I'll give it another go.

copy frag n skip should be perfectly OK

hmm.  that works.  except I miss the last piece of the text as if 
last piece less than n, it doesn't get copied.

example of what you get and what want?

split-text "this is a sentence" 11
[]

I want [ "this is a sentence" ]

how about:

    copy frag [to #" " | to end]

yah! that works.

I tried putting in an alternate rule of " | copy frag to end " but 
that hung the parser.

this should work too:

    [copy frag #" " | copy frag to end]