On Mon, Jan 28, 2019 at 11:49 AM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Yet even there you did a great job of rethinking the thing that handles
> the data, leaving the data free to be as free as data often is.
>
Thanks! It was a pain to format, but my
Geoff Canyon wrote:
> Sure, I'm not arguing for custom property sets -- just saying that if
> you *are* going to use them, don't bork the naming convention.
Names of prop sets, or the names of keys within a set?
On the latter I have mixed feelings.
As you know, I have rather a fetish about
I mean to say the first (and only I am sorry to say) Revolution conference I
attended. That sounded like I put on a conference myself. :-)
Bob S
> On Jan 28, 2019, at 08:02 , Bob Sneidar via use-livecode
> wrote:
>
> This was addressed in my first Revolution conference.
This was addressed in my first Revolution conference. One of the classes was
about naming conventions. Not only do you have to be careful about your names
clashing with built-in names, but also reserved words, and the names used by
OTHER developers (think plugins).
Other languages partially
Yes. I'm scared as well about naming things :) I'm not sure what is safe.
Thee is a tension between making your code readable, and worrying that your
use of a natural language term will clash with some evolution of the
language that may later get added as a native feature. Is nothing safe?
On
Sure, I'm not arguing for custom property sets -- just saying that if you
*are* going to use them, don't bork the naming convention.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage
Hi Geoff, for me the solution is to have a naming convention for all of a
developers / projects work - so everything is prefixed by 4 letters, and
then in the case of custom properties / custom property sets - to migrate
off them and just stick to arrays. The custom property / set syntax was