Strict Compilation Mode
Ender Nafi Elekcioglu
endernafi at gmail.com
Thu Dec 5 22:40:08 EST 2013
I have many strict rules about naming conventions and style of code, organizations of cards, usage of groups, etc.
But my co-workers don’t care those scripting rules much
and their lack of attention -especially typos- make debugging process a headache.
Besides, I wanted our projects to be future-proof.
One after another their scopes get wider, line count of codes increase constantly.
So far, I’m pretty happy with Strict Compilation Mode on.
~ Ender Nafi
On December 6, 2013 at 5:24:01, Robert Sneidar (slylabs13 at me.com) wrote:
This has been hashed out before, but I think that if you are not using strict compilation mode from the git go, it would probably be better if you didn’t switch. Unless you are writing a fairly complex application, there really is not any reason (that I can see) for using strict compilation mode. It’s not that difficult to keep track of your variables if you develop a standard naming convention.
On Dec 5, 2013, at 8:40 AM, Dr. Hawkins <dochawk at gmail.com> wrote:
> On Mon, Dec 2, 2013 at 2:40 PM, Ender Nafi Elekcioglu
> <endernafi at gmail.com>wrote:
>> I’ve changed a couple of lines deliberately and it compiled again.
> That can help.
> Breaking apart the line that declares the variable can help.
> In 5.5, quiting & restarting livecode usually helps. In any version of 6
> I've tried, it's just nightmare; this is why I'm still using 5.
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode