Re: records
Re: records
- Subject: Re: records
- From: Daniel Shockley <email@hidden>
- Date: Fri, 2 Mar 2001 14:16:43 -0800 (PST)
>
Message: 6
>
Subject: Re: Records
>
From: Simon Forster <email@hidden>
>
>> listToRecord({"firstName", "Dan", "lastName", "Shockley"})
>
>> -- returns {|firstName|:"Dan", |lastName|:"Shockley"}
>
>
>
>It would appear that you have to use all lowercase letters for property
>
>names - at least using Olof's method.
>
>Simon is right. Darned shame really. That's probably a deal killer for what I
>
>want to use it for. Oh well.
>
>
Aww, c'mon fellas! Turn those frowns upside down! Is it really a purely
>
a case of case inspiring those rainy day attitudes?
>
>
Seems you've overlooked a minor detail.
>
>
Uppercase, lowercase, It's all the same to AppleScript which
>
is not case sensitive, well as far as symbols (variable names)
>
are concerned.
>
>
The first time you declare a variable, the capitalization is
>
noted and any variation using the same letters compiles to
>
your initial arrangement:
>
usrf names are always transmitted in lowercase, but if you declare the
>
variable first you'll get the aesthetic result you want:
>
If you wanted to be able to create records from _outside_ input, you wouldn't know what the
property names are goign to be ahead of time. If you have to know what they are to use this
method, it defeats a major point, which is to not have to know.
If I knew what the property names were going to be, I could just define them in the record
directly. It's when I don't know what they will be that this becomes most useful.
So, this will reduce the usefulness of the usrf method of creating records. Darn! :-(
Unless somebody has a way around it? I suppose I could change the case to lower-case before I make
the user-record, but then that might cause other problems.
=====
Daniel A. Shockley
email@hidden
http://www.danshockley.com
http://www.krioni.com
And now for a message from my sponsor... *grin*
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/