Hi Max,
> why use switch rather than select?
>
> I can use code when I need it, directly in my values.
>
> default-value: "n/a"
>
> data: [name [default-value] age [30] race ["beagle"]]
> name: switch 'name data
> == "n/a"
>
> also, the fact that values are within blocks makes the use of words as
Hi Ashley,
Interesting samples and comments.
> I also try to store as much meta-data in the file-system as I can, for
> example, I may have a file like the following:
>
> /c/rSQL/Contacts/Name.s24
>
> which tells me that the "Contacts" table has a "string" column of 24
> characters width named "
I often use objects and store them on disk as code using mold.
With rebol writing text files is so easy.
but for larger data, I usually then go with blocks. using switch like so:
data: [name ["snoopy"] age [30] race ["beagle"]]
name: switch 'name data
== "snoopy"
I know many use blocks of t
Hi Brett, a topic near and dear to me ;)
For me, I find the model I choose is impacted by:
- data structure
- volume
- time [development]
- performance requirements
- whether the data is static / dynamic
For key / value pairs I might use:
states: ["VIC" "Victoria" "NSW" "New South Wale
