Re: Backwards compatibility or sanity? help

> On 24 Aug 2016, at 10:39 PM, Kay C Lan wrote: > > As does this situation where combine/split doesn't round-trip That’s a good one! http://quality.livecode.com/show_bug.cgi?id=18259

Re: Backwards compatibility or sanity? help

On Sun, Aug 21, 2016 at 7:52 AM, Monte Goulding wrote: > >> On 21 Aug 2016, at 9:38 AM, Randy Hengst wrote: >> >> This doesn’t totally fit with the conversation, and I assume the Team knows >> this but… SORT assumes that a trailing comma indicates an empty

Re: Backwards compatibility or sanity? help

On 21/08/2016 00:22, Monte Goulding wrote: On 21 Aug 2016, at 8:57 AM, Richard Gaskin wrote: > > It would appear that the current behavior in v8 is a fix that addresses a previously anomalous handling of delimiters in the case of "is among". That’s my feeling also.

Re: Backwards compatibility or sanity? help

Thank you all very much for the detailed and patient information. Yes, there was a big misunderstanding about RTL/LTR by me, because language-script directions can be deliberately mixed ('bidirectional', as I read in an LC 7 introductory blog). >From that I concluded erroneously a wrong in-memory

Re: Backwards compatibility or sanity? help

On 21/08/2016 15:26, hh wrote: > Ali, > probably it's about time that you give at RTL-lesson/blog/tutorial? > Would be very appreciated. > >> Ali wrote: >> the number of items in 'ab' is not an invariant of its read order, >> unless you reverse the characters in the delimiter too. >> When the item

Re: Backwards compatibility or sanity? help

Perhaps there's a misunderstanding here... If when you refer to rtl to mean rtl languages (such as Arabic) then there is nothing to do - rtl languages are stored in memory in logical order - ie the same way round as ltr languages. It is just the display which is changed. If you mean doing

Re: Backwards compatibility or sanity? help

Ali, probably it's about time that you give at RTL-lesson/blog/tutorial? Would be very appreciated. > Ali wrote: > the number of items in 'ab' is not an invariant of its read order, > unless you reverse the characters in the delimiter too. > When the item delimiter is 'aa', the items of 'baaa'

Re: Backwards compatibility or sanity? help

Hermann, Symmetric chunks of the type you describe have issues when the delimiting rules are more complex - for example when the item delimiter is 'ab', the number of items in 'ab' is not an invariant of its read order, unless you reverse the characters in the delimiter too. When the item

Re: Backwards compatibility or sanity? help

> Monte wrote: > Hmm... I've got to say I'm a little on the ignorant > side of things with regard to RTL text in LiveCode but > my understanding is it's only a field thing and any > chunk references are always LTR. Happy to be educated > though! Sorry Monte, I thought (erroneously?) that

Re: Backwards compatibility or sanity? help

Hmm... I've got to say I'm a little on the ignorant side of things with regard to RTL text in LiveCode but my understanding is it's only a field thing and any chunk references are always LTR. Happy to be educated though! Cheers Monte Sent from my iPhone > On 21 Aug 2016, at 6:06 PM, hh

Re: Backwards compatibility or sanity? help

> > Hermann wrote: > > Why is the number of items or having the property "item" > > of a string dependent on the writing/reading direction > > of the string? > Monte wrote: > Hmm… I’ll answer your question with a question: Which item is item 1? The string "a," has currently .. [RTL] ..

Re: Backwards compatibility or sanity? help

> On 21 Aug 2016, at 9:52 AM, Monte Goulding wrote: > > Oh yay…. this behavior persists in LiveCode 8. There is an ANOMALY report on this: http://quality.livecode.com/show_bug.cgi?id=16588

Re: Backwards compatibility or sanity? help

> On 21 Aug 2016, at 9:46 AM, hh wrote: > > Why is the number of items or having the property "item" > of a string dependent of the writing/reading direction > of the string? Hmm… I’ll answer your question with a question: Which item is item 1? Cheers Monte

Re: Backwards compatibility or sanity? help

> On 21 Aug 2016, at 9:38 AM, Randy Hengst wrote: > > This doesn’t totally fit with the conversation, and I assume the Team knows > this but… SORT assumes that a trailing comma indicates an empty item Oh yay…. this behavior persists in LiveCode 8.

Re: Backwards compatibility or sanity? help

Why is the number of items or having the property "item" of a string dependent of the writing/reading direction of the string? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your

Re: Backwards compatibility or sanity? help

This doesn’t totally fit with the conversation, and I assume the Team knows this but… SORT assumes that a trailing comma indicates an empty item… for example: on mouseUp local tTestITEMS put "1,2,3,4,5," into tTestITEMS answer the number of items in tTestITEMS && "ITEMS" &&

Re: Backwards compatibility or sanity? help

> On 21 Aug 2016, at 8:57 AM, Richard Gaskin wrote: > > It would appear that the current behavior in v8 is a fix that addresses a > previously anomalous handling of delimiters in the case of "is among". That’s my feeling also. We know it impacts a popular library

Re: Backwards compatibility or sanity? help

Monte Goulding wrote: >> On 21 Aug 2016, at 8:47 AM, Richard Gaskin wrote: >> >> The current behavior for Trevor's test is consistent with item >> counts. If we change it we open up that can of worms about >> delimiters all over again, and undo Mark's thinking on this. > > Yes the point is

Re: Backwards compatibility or sanity? help

> On 21 Aug 2016, at 8:47 AM, Richard Gaskin wrote: > > The current behavior for Trevor's test is consistent with item counts. If we > change it we open up that can of worms about delimiters all over again, and > undo Mark's thinking on this. Yes the point is

Re: Backwards compatibility or sanity? help

Monte Goulding wrote: > The team is in a quandary about the following bug: > > http://quality.livecode.com/show_bug.cgi?id=18145 > > The issue is in LiveCode 6.7 and below `is among` was essentially > implemented incorrectly meaning that you could get results like this: > > put the number of

Backwards compatibility or sanity? help

Hi LiveCoders The team is in a quandary about the following bug: http://quality.livecode.com/show_bug.cgi?id=18145 The issue is in LiveCode 6.7 and below `is among` was essentially implemented incorrectly meaning that you could get results