Another thing to try that helped me more than once is to copy/paste the script
(the ENTIRE script not just the handlers) into a text file formatted for Text
Only then copy/paste it back into your script replacing what is there. I think
it has something to do with the unicode text thingummy.
Bob
To: How to use LiveCode
Subject: Re: compiler not catching bad exit within routine
On Wed, Dec 7, 2016 at 3:21 AM, Dave Kilroy
wrote:
> Have you tried checking your script for invisible characters? Try
> copying the entire script to something like BBedit, selecting and
> copying it afr
On Wed, Dec 7, 2016 at 3:21 AM, Dave Kilroy
wrote:
> Have you tried checking your script for invisible characters? Try copying
> the entire script to something like BBedit, selecting and copying it afresh
> there, deleting everything in the LiveCode script, saving it to ensure it's
> clean, pasti
Or try this if the script is not supposed to have any non-ascii characters:
local tLineCount, tCPCount
repeat for each line tLine in
Ah right I get it now
Have you tried checking your script for invisible characters? Try copying
the entire script to something like BBedit, selecting and copying it afresh
there, deleting everything in the LiveCode script, saving it to ensure it's
clean, pasting in the (hopefully cleaned) script f
On Tue, Dec 6, 2016 at 4:01 PM, mwieder wrote:
> My guess is that there's a "makeNewDnaRec" variable somewhere in the
> original script.
>
just checked; and no.
And strict compilation is on (although it seems to keep getting turned off).
--
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
Yeah, I think that's the point of the original post.
My guess is that there's a "makeNewDnaRec" variable somewhere in the
original script.
-
--
Mark Wieder
ahsoftw...@gmail.com
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/compiler-not-catching-bad-exit
On Tue, Dec 6, 2016 at 3:03 PM, Ali Lloyd wrote:
> I've no idea what the problem could be, but when things like this happen to
> me I copy the routine and continually delete lines until either I discover
> what I did wrong, or have a very minimal test case.
>
That's my usual approach, but it fa
On Tue, Dec 6, 2016 at 2:52 PM, Dave Kilroy
wrote:
> You define a handler "mkNwDnaRec" but your exit statement refers to
> "makeNewDnaRec" ...
>
>
Correct.
That should throw any error on script save--but it doesn't.
The rest of the script compiles, but this routine quietly doesn't.
--
Dr.
You define a handler "mkNwDnaRec" but your exit statement refers to
"makeNewDnaRec" ...
-
"The first 90% of the task takes 90% of the time, and the last 10% takes the
other 90% of the time."
Peter M. Brigham
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/c
I've no idea what the problem could be, but when things like this happen to
me I copy the routine and continually delete lines until either I discover
what I did wrong, or have a very minimal test case.
On Tue, Dec 6, 2016 at 9:30 PM Dr. Hawkins wrote:
> I have a (much longer) routine to the nat
11 matches
Mail list logo
