Strange behavior of the IDE?

[Graham Samuel]

Just in case anyone is interested in this topic:

1. I reported it as a bug and it's been accepted (11861).

2. It looks like my error, which triggered the IDE issue, was probably this statement:

  put @ into t1

where I had meant to write

  put "@" into t1

The "@" character has some meaning to LC - from the Dictionary:

> The character @ (at sign) is used with a parameter declaration, to indicate that a reference to the parameter is passed instead of its value.

Seems to be way outside any conceivably correct context. Ah well.

Just FYI

Graham

On 27 Feb 2014, at 23:59, Graham Samuel <livfoss at mac.com> wrote:

> Kay, thanks to you and everyone who replied. I see that your technique will isolate the issue, since I suppose logically it must be in my code. It's extraordinary though that the IDE just caves in in certain circumstances without any form of error report when the program is obviously running wild (after all, it's interpreted... but let's not get too deeply into that). Let's hope future versions of the IDE will be a bit more helpful. Meanwhile I will take the advice I've been given.
> 
> Cheers
> 
> Graham
> On 27 Feb 2014, at 23:08, Kay C Lan <lan.kc.macmail at gmail.com> wrote:
> 
>> On Fri, Feb 28, 2014 at 3:03 AM, Graham Samuel <livfoss at mac.com> wrote:
>> 
>>> The first line of the function has a breakpoint in it, but as soon as
>>> execution moves to the function, none of the breakpoints within it apply.
>>> 
>>> As stated there is a syntax/logic error in the function. As Peter said put
>> a hard breakpoint as line 1 of the function, then comment out every other
>> line. You will now be able to step into the function - which proves there
>> is a problem within it*. Then systematically uncomment 50% of the commented
>> code. You should be able to quickly locate where the offending line is once
>> you are able to actually step into your function.
>> 
>> * On very rare occasions, I'm pretty sure associated with copying and
>> pasting code from online, I've had functions or scripts that don't behave
>> as they should. In this case I've cut the function/handler, or in extreme
>> cases the entire script out and pasted it into a text editor -
>> TextWrangleran excellent free one for Mac. I 'Apply' and Saved the
>> stack with the
>> offending piece missing. I then use BBEdit's (TextWranglers big brother)
>> Zap Gremlins function to remove all non ASCII, ASCII control and ASCII null
>> values. I then reinsert the code which is now plain vanilla text, 'Apply'
>> then save and things return to normal.
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode