At 8:12 PM -0500 1/8/2001, Kurt Griffin wrote:
>
>When I feel the urge to put an integer as a property into a prop list (you
>know, I've never really found a problem with integers as properties, but
>it's considered bad form - maybe you just found out why?), I usually make a
>"sequential string" - like "url1", "url2", etc. - it doesn't take much to
>change propList.addProp(i, myUrl) to propList.addProp("url" & i, myUrl), and
>so on. And I think it always helps to give properties descriptive names,
>IMHO.
Well, in the strictest sense if I understand what grimm was doing
(which scares me a bit... ;-) he was *not* specifying integers as
properties in a property list.
He was specifying netIDs which happened to be integers. Same with
Jacob's example of the markerList.
Every property (integer) in those lists is guaranteed to be unique. I
don't see why its bad form or why you would want to much it up by
coercing it into a string.
/r
--
Roy Pardi
---------------------------------------------------------------
Contract Multimedia Developer + Lingo Programmer
[EMAIL PROTECTED]
---------------------------------------------------------------
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
