On Tue, 26 Dec 2000, Patrick Dughi wrote:
>name_of_array = { name_of_array2 = {
> "entry 1", {"entry 1",1},
> "entry 2", or {"entry 2",2},
> "entry 3" {"entry 3",4}
>} }
[...]
><constant="name_of_array">
> "entry 1"
> "entry 2" etc
> "entry 3"
></constant>
LISP-style. :)
(name_of_array (entry1 12) (entry2 25) (entry3 30))
You can emulate HTML-like markup like:
(A
(HREF http://www.circlemud.org/)
(TARGET _new)
(TITLE "CircleMUD Web Site")
)
C-style might encourage people to try tricks (e.g., pre-processor) that
only works in real C. The advantage would be cut & paste portability of
the structures between the MUD and the editor. I'd rather most of the
constant arrays in CircleMUD be flat files anyway, but for now it's C code.
MarkUp-style; unless you're doing it in Perl (HTML::Parser is sweet),
I don't see an advantage to parsing it that LISP doesn't have easier. In
addition, some editors will parenthesis match for you if you need it.
Foobar^1-delimited flat files for each table isn't bad either. I mean, why
does:
const char *weekdays[] = {
"the Day of the Moon",
"the Day of the Bull",
[...]
have to be in a C file in the first place?
--
George Greer | If it's about the CircleMUD mailing list,
greerga@circlemud.org | mail owner-circle@post.queensu.ca instead.
1: Pick a character, any character. Tab and comma being common.
--
+---------------------------------------------------------------+
| FAQ: http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
| Archives: http://post.queensu.ca/listserv/wwwarch/circle.html |
+---------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 04/11/01 PDT