I lost a bit of time trying to reproduce the issue using an input
actually having NULLs, and could not reproduce.
The recipe is way simpler, and the bug report is there:
http://quality.runrev.com/show_bug.cgi?id=15641
Regards,
Seb
On 23/07/2015 15:32, Mark Waddingham wrote:
Indeed - I
On 7/23/2015 1:11 AM, Peter Bogdanoff wrote:
A heads up:
split tText by cr and null
works differently in LiveCode 7 than it did in LC 6. The cr parameter is OK,
but the null adds another cr when this expression is used in LC 7.
I am trying to understand what the intent is/was of
Sounds like it's time for a bug report.
On Thu, Jul 23, 2015 at 1:11 AM, Peter Bogdanoff bogdan...@me.com wrote:
A heads up:
split tText by cr and null
works differently in LiveCode 7 than it did in LC 6. The cr parameter is
OK, but the null adds another cr when this expression is
Indeed - I already forwarded this to Seb to file :)
Sent from my iPhone
On 23 Jul 2015, at 15:28, Mike Kerner mikeker...@roadrunner.com wrote:
Sounds like it's time for a bug report.
On Thu, Jul 23, 2015 at 1:11 AM, Peter Bogdanoff bogdan...@me.com wrote:
A heads up:
split
Moreover, that example succeeds in LC 7!
On Thu, Jul 23, 2015 at 4:04 PM Paul Dupuis p...@researchware.com wrote:
On 7/23/2015 1:11 AM, Peter Bogdanoff wrote:
A heads up:
split tText by cr and null
works differently in LiveCode 7 than it did in LC 6. The cr parameter is
OK, but
Hi Peter,
After looking more into the issue, it appears that you have been
exploiting a bug in LiveCode 6.7 for a long time, that's not a bug in
LiveCode 7.0 :)
If you change
by NULL
with
by ;
then you will have the same thing in 6.7 as you see with NULL in 7.0:
the behaviour
