Re: Chunk order must be small to large

Richard Gaskin wrote: It may be tempting to want to implement some custom behavior for, say, the truncate function. Raney felt that all that did is risk confusing anyone who calls that function while your handler is in the message path, so in his view it didn't merely expode the size

Re: Chunk order must be small to large

Richard Gaskin wrote: I went to the mat with him over this one years ago when I was porting an HC project. He said, If you need a custom behavior, use a custom name. I said, But I *need* to override the built-in function! and he asked simply, 'Need'? Why? I couldn't think of a truly

Re: Chunk order must be small to large

Ben Rubinstein wrote: Richard Gaskin wrote: I went to the mat with him over this one years ago when I was porting an HC project. He said, If you need a custom behavior, use a custom name. I said, But I *need* to override the built-in function! and he asked simply, 'Need'? Why? I

Re: Chunk order must be small to large

I dug out my old copy of the v.2 User Guide. This guide has stuff in it that the v.3 guide does not. It has a short section on Complex chunk expressions, where it states: - chars can't contains words - words can't contain items - items can't contain lines Now I know what must be small to large

Re: Chunk order must be small to large

DunbarX wrote: I dug out my old copy of the v.2 User Guide. This guide has stuff in it that the v.3 guide does not. It has a short section on Complex chunk expressions, where it states: - chars can't contains words - words can't contain items - items can't contain lines Now I know what

Re: Chunk order must be small to large

Richard Gaskin wrote: Ben Rubinstein wrote: ... ... a simple statement, legal in the syntax, which crashed Rev with 100% reliability shouldn't be marked critical because it could only affect the programmer, who should know better. What statement is that, and has it been fixed? See

Re: Chunk order must be small to large

planets can't contain suns mice can't contain cats leaves can't contain trees etc. ad nauseam ROFL. :-) Bob Sneidar IT Manager Logos Management Calvary Chapel CM On Mar 13, 2009, at 10:12 AM, dunb...@aol.com wrote: - chars can't contains words - words can't contain items - items can't

Re: Chunk order must be small to large

On Mar 13, 2009, at 10:53 AM, Bob Sneidar wrote: planets can't contain suns mice can't contain cats leaves can't contain trees etc. ad nauseam ROFL. :-) Ah, but mice can, and have, contained chunks of cats. Jim Ault Las Vegas ___ use-revolution

Re: Chunk order must be small to large

Craig- Friday, March 13, 2009, 10:12:27 AM, you wrote: This guide has stuff in it that the v.3 guide does not. It has a short section on Complex chunk expressions, where it states: - words can't contain items Don't believe everything you read, though... set the itemdelimiter to comma put

Re: Chunk order must be small to large

From the dictionary in OSX 2.9 Word Designates a space-delimited or quoted string as part of a chunk expression. hello,sailor,new,in,town? has no spaces and thus is only one word. On Mar 13, 2009, at 2:08 PM, Mark Wieder wrote: Craig- Friday, March 13, 2009, 10:12:27 AM, you

Re: Chunk order must be small to large

Mark, 1 and 5, no? Craig Newman In a message dated 3/13/09 5:10:50 PM, mwie...@ahsoftware.net writes: - words can't contain items Don't believe everything you read, though... set the itemdelimiter to comma put the number of words in hello,sailor,new,in,town? put the number of items

Re: Chunk order must be small to large

Mark, Oh, I see. Words containing items. Literal strings without spaces of course are one word. But still, another scriptJoke. And a good one. Craig Newman In a message dated 3/13/09 5:10:50 PM, mwie...@ahsoftware.net writes: Don't believe everything you read, though... set the

Re: Chunk order must be small to large

Jim- Friday, March 13, 2009, 2:28:32 PM, you wrote: From the dictionary in OSX 2.9 Word Designates a space-delimited or quoted string as part of a chunk expression. hello,sailor,new,in,town? has no spaces and thus is only one word. Exactly. Yet it contains six items... -- -Mark

Re : Chunk order must be small to large

Hi from Paris, Take for example 5 * 5 + 1. Did we mean (5 * 5) + 1? Or did we mean 5 * (5 + 1)? Well we know by math formula rules that the multiplication is calculated first, so 26 is the correct answer. It would have been clearer to just use the parenthesis and avoid any confusion, and many

Re: Re : Chunk order must be small to large

Translating British into English is always interesting. PEMDAS parentheses,exponentiation,mult/div,add/subt Craig Newman On Mar 13, 2009, at 7:24:35 PM, Francis Nugent Dixon effe...@wanadoo.fr wrote: Brackets Off/Divide/Multiply/Add/Subtract I don't think that the rules have changed

Chunk order must be small to large

: bad chunk order (must be small to large) If I write: answer word 1 of item 1 of it, Rev (like HC) yields aaa, but that is hardly solace. Make my day. Craig Newman ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url

Re: Chunk order must be small to large

In a message dated 3/12/09 11:16:10 AM, m.schonewi...@economy-x-talk.com writes: Mark. Sure. Just couldn't resist. I usually debug long convoluted constructs (word item 3 of line whatever) by adding parentheses just to see where the breakdown (usually mental) occurs. This one seemed so

Re: Chunk order must be small to large

Stephen; Right. I was cavalier in thinking I can validate Rev issues by emulating them in HC. This is not fair to Rev. I like parentheses. But is this really a bug? Or just the way the parser works? I have many constructs in HC (get word line item 3 of the...) and I hope that this probably

Re: Chunk order must be small to large

dunb...@aol.com wrote: Stephen; Right. I was cavalier in thinking I can validate Rev issues by emulating them in HC. This is not fair to Rev. I like parentheses. But is this really a bug? Or just the way the parser works? I have many constructs in HC (get word line item 3 of the...) and I

Re: Chunk order must be small to large

, Chunk order must be small to large and it may have had to do with the internal mechanics of the parser, but more likely it was to keep us from saying things that had no meaning. I mean, how much sense would it have made to say, 'the short name of stack toobig of card toosmall', or 'word 1

RE: Chunk order must be small to large

...@lists.runrev.com] On Behalf Of dunb...@aol.com Sent: Thursday, March 12, 2009 7:01 AM To: use-revolution@lists.runrev.com Subject: Re: Chunk order must be small to large Stephen; Right. I was cavalier in thinking I can validate Rev issues by emulating them in HC. This is not fair to Rev

Re: Chunk order must be small to large

Jim Bufalini wrote: ... And this is logical as, a. You can set itemDelimiter and lineDelimiter but not the word delimiter (smallest chunk, which word boundary has undergone a change recently in Rev 3.0), b. When parsing text, words are generally smaller chunks than phrases, which are usually

Re: Chunk order must be small to large

And I never saw this problem because I intuitively use parentheses! Stephen Barncard - San Francisco http://barncard.com 2009/3/12 Richard Gaskin ambassa...@fourthworld.com Jim Bufalini wrote: ... And this is logical as, a. You can set itemDelimiter and lineDelimiter

RE: Chunk order must be small to large

from Hawaii, Jim Bufalini -Original Message- From: use-revolution-boun...@lists.runrev.com [mailto:use-revolution- boun...@lists.runrev.com] On Behalf Of stephen barncard Sent: Thursday, March 12, 2009 6:24 PM To: How to use Revolution Subject: Re: Chunk order must be small to large