Thanks Mark, sounds like a stye thing then. I love it when real programmers post on this list - what is DRY code?
Not really on topic, but whatever happened to decision table processors? I used one years ago and found it to be a great way to express complex if statements and their related actions. Pete lcSQL Software <http://www.lcsql.com> On Sun, Jan 27, 2013 at 12:31 PM, Mark Wieder <mwie...@ahsoftware.net>wrote: > Pete- > > Sunday, January 27, 2013, 11:45:16 AM, you wrote: > > > OK, so I understand the parens thing now. Any thoughts on the use of > > multiple ifs vs joining the conditions together with "and". I've > > always considered that to be just a matter of personal preference and > ease > > of reading but wondering if there might be other implications, like > > performance for example. > > No performance hits. They compile down to the same code. In some > situations one may be easier to read than the other or vice versa. I > usually use the separate lines form to make it easier to maintain if I > have to add things. I also find that separating them this way makes it > easier to write DRY code since conditions in common stand out more. > > -- > -Mark Wieder > mwie...@ahsoftware.net > > > _______________________________________________ > 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 > _______________________________________________ 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