Message 14 on *C& Group (#72879):
Date: Thu Mar 6 14:00:26 2003 PST
From: TEf (#69976)
To: *C& Group (#72879)
Some issues that have stalled me working on something like this (and
I've had it in the back of my head for a long long time):
It's commonly viewed by language purists that "end" structure keywords
are stupid. In light of this, I'd be tempted to remove
if/endif,while/endwhile,etc constructs and go toward a more unified
single syntax block structure (using { and }). This would help
adoption, but it also makes the language look like just about every
other one.
There currently is no syntax to define objects in "the MOO programming
language", by it's very nature. It's instructive, not declarative.
This is a major stumbling block in my book, because it requires a big
chuck of syntax to be designed and written.
I'd lean toward an interpretive environment rather than compilative.
Not only for legacy reasons, but for the same reason that a perl
complier exists and doesn't see as much use as otherwise: plain ol'
interpreted perl is fast enough, and more portable.
Library definitions. Compare anything you want to do to Perl's CPAN or
PHP's PEAR. CPAN, in particular, is a fucking nightmare for packaging
systems (as if perl wasn't, ha!). I personally prefer dynamic loading
(ala PHP and apache for extensions), in order to customize at
run/loadtime, but perl's legacy c-like .so with C-like API interface
descriptions (.pm) has always given me trouble, not from a use
standpoint, but a maintainence standpoint. Rather than do a PHP-esque
'.so that defines new builtin functions', the ability to have MOO
methods/verbs bind to native code in a .so would be cleaner from a
language standpoint (PHP is a mess in this reguard, IMO).
--------------------------
#############################################################
This message is sent to you because you are subscribed to
the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to <[EMAIL PROTECTED]>
