Strict Compilation Mode

Peter Haworth pete at lcsql.com
Fri Dec 6 11:08:48 EST 2013


I switched to strict compilation mode after doing without it for months.
The conversion process revealed several typo errors which would have
eventually revealed themselves as bugs.  For me the benefits far outweigh
the minor inconveniences and I would never switch back.

There was a recent post from someone saying his company would not use any
LC tools that would not compile with strict compilation mode on.

I wrote myself a stack which will analyze a script  and create any missing
local statements while attempting to identify typos in variable names. It
made it a lot less time consuming to convert to strict compilation mode. If
anyone would like a copy, email me off list.

Pete
lcSQL Software
On Dec 5, 2013 7:40 PM, "Ender Nafi Elekcioglu" <endernafi at gmail.com> wrote:

> 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.
>
>
>
> Best,
>
> ~ 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.
>
> Bob
>
>
> 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:
> > 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
> _______________________________________________
> 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



More information about the Use-livecode mailing list