-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 26 November 2003 06:40, Tanaka Akira wrote:
> > The "secret" keys aren't clearly defined in the API.  IE, you don't have
> > a clear list of what the arguments are.
>
> Isn't it documented?

Yes, and as we all know, the documentation is *always* kept up to date.

> Interesting.  But I couldn't find such questions in ruby-talk.
> (I grepped '=>' in ruby-talk mails which contains your e-mail address.)

There is a separate mailing list for REXML, and I get quite a number of direct 
correspondances, as well.  I'd guess that less than 10% of the REXML 
discussion occurs in ruby-talk.

> Would you give me some example references?

I can forward emails, if you like.  They're mostly not complaints about the 
hash-ed nature of the arguments, but rather "how do I do this", and "I can't 
get this to work", and "how does this work?"

> > Which problem do you mean?  From the developer's point of view, or from
> > the Ruby interpreter's point of view?
>
> For the developper.

The problem is in handling polymorphic methods.   Ruby doesn't support method 
polymorphism, meaning that to have method foo() that takes EITHER a string 
and an optional int, OR a Foo and an optional String and an optional int, I 
have to produce some pretty complex code to handle the various possible 
states.

- -- 
### SER   
### Deutsch|Esperanto|Francaise|Linux|XML|Java|Ruby|Aikido|Dirigibles
### http://www.germane-software.com/~ser  jabber.com:ser  ICQ:83578737 
### GPG: http://www.germane-software.com/~ser/Security/ser_public.gpg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/yOHuP0KxygnleI8RAi/nAJ9yXhFGQe2+3yB3+RwVIGLglEHTUACfTSqp
qtwgZSKDj7235P1fHADv3Z0=
=Bkl/
-----END PGP SIGNATURE-----