Dr. Dobbs Article

I just received the latest DDJ which contained an article titled
"Databases & Dynamic Ruby Classes." I haven't had the chance to read
it (too busy), but it was good to see Ruby getting more exposure.
(Especially in a magazine such as DDJ)

Just an fyi for the group.

-andy

Andy Stone wrote:

I just received the latest DDJ which contained an article titled
"Databases & Dynamic Ruby Classes." I haven't had the chance to read
it (too busy), but it was good to see Ruby getting more exposure. (Especially in a magazine such as DDJ)

Just an fyi for the group.

-andy

What Vol number, etc? Tell us if its a good article, thanks. :wink:

David Ross

···

--
Hazzle free packages for Ruby?
RPA is available from http://www.rubyarchive.org/

Well I just read it. Pretty interesting. It was about using
method_missing to do DB updates (ie something.property =
something_else, update the DB at the key propety, etc.) and some
interesting stuff about storing ruby code in the database as opposed
to in the source. Pretty neat.

···

On Fri, 5 Nov 2004 11:23:01 +0900, Andy Stone <xsltguru@gmail.com> wrote:

I just received the latest DDJ which contained an article titled
"Databases & Dynamic Ruby Classes." I haven't had the chance to read
it (too busy), but it was good to see Ruby getting more exposure.
(Especially in a magazine such as DDJ)

Just an fyi for the group.

-andy

To me, as a ruby slightly-post-newby, method_missing is a unique and
powerfull feature that makes ruby feel like a truely 'real' OO
language. That is message passing rather than method calls with
implicit this objects.

I love it! If only you could catch java.lang.NoSuchMethodError in the
callee rather than the caller...

···

On Fri, 5 Nov 2004 11:45:25 +0900, Logan Capaldo <logancapaldo@gmail.com> wrote:

Well I just read it. Pretty interesting. It was about using
method_missing to do DB updates (ie something.property =
something_else, update the DB at the key propety, etc.) and some
interesting stuff about storing ruby code in the database as opposed
to in the source. Pretty neat.

On Fri, 5 Nov 2004 11:23:01 +0900, Andy Stone <xsltguru@gmail.com> wrote:
> I just received the latest DDJ which contained an article titled
> "Databases & Dynamic Ruby Classes." I haven't had the chance to read
> it (too busy), but it was good to see Ruby getting more exposure.
> (Especially in a magazine such as DDJ)
>
> Just an fyi for the group.
>
> -andy
>
>

Since java is a strongly typed language that won't happen :confused: The method
must exist on the receiver. You're probably already aware of it, but you
can do something similar by using dynamic proxies in java. Check out
java.lang.reflect.Proxy and java.lang.reflect.InvocationHandler.

[snip]

//Anders

···

On Fri, Nov 05, 2004 at 11:57:08AM +0900, Lyndon Samson wrote:

To me, as a ruby slightly-post-newby, method_missing is a unique and
powerfull feature that makes ruby feel like a truely 'real' OO
language. That is message passing rather than method calls with
implicit this objects.

I love it! If only you could catch java.lang.NoSuchMethodError in the
callee rather than the caller...

--
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. Anders Engström aengstrom@gnejs.net
. http://www.gnejs.net PGP-Key: ED010E7F
. [Your mind is like an umbrella. It doesn't work unless you open it.]