Alex, I'm sure that one of the problems that faces most new LC coders is that they do too much before they try it out. By the time I have something "done" I've already debugged it dozens of times. It just works. Of course I don't stretch LC to its limits very often. When I do something, I've done it at least a dozen times before and am very sure it "almost" works as I've done it, so my own commenting is pretty limited. (smile)
How's the weather in Brazil? It's in the 70s here in Southern California, so I can't gripe. Joe Wilkins Architect On Feb 18, 2012, at 5:11 PM, Alejandro Tejada wrote: > Hi Joe, > > > Joe Lewis Wilkins wrote >> >> True Ken, but w/o comment it is much more difficult to know what is going >> on. >> If you're going to use one liners like this, you'd better add some >> commentary. >> One of the weaknesses I see in LC coding is the shortage of comments. >> I realize that is a strong-point of LC; it is "almost" self-commenting, >> but... >> > > Well, maybe the standard method to understand code is to debug it. > > Could you imagine a stack that run a script and at the same time, > it explained how it works, step by step? > > Is this science fiction or does actually exists something > like that in some development platform? > > Does exist Linting software for this language? > (Besides the Livecode own compiler) > http://en.wikipedia.org/wiki/Lint_(software) > > Al _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
