From: Ilias Lazaridis <ilias@...>
Date: 2011-06-01T18:15:29+09:00
Subject: Re: CORE - Specialized Attribute Definition

On 1 Ιούν, 11:28, Josh Cheek <josh.ch...@gmail.com> wrote:
> 2011/6/1 Ilias Lazaridis <il...@lazaridis.com>
> > On 31 ÌÜúïò, 17:26, Josh Cheek <josh.ch...@gmail.com> wrote:
> > > [Note:  parts of this message were removed to make it a legal post.]
>
> > > On Tue, May 31, 2011 at 8:05 AM, Ilias Lazaridis <il...@lazaridis.com
> > >wrote:
>
> > > > ruby 1.9
>
> > > > (this is about the *abilities* or the ruby 1.9 language)
>
> > > > class Persnon
> > > >  attrib name  String opt1 opt2
> > > >  attrib age Integer
> > > > end
>
> > > > The main questions:
> > > > a) Can such an "attrib" method be implemented with ruby code?
> > > > b) Can such an "attrib" functionality be implemented on the C-level
> > > > (as extension, not as modification of source)?
>
> > > > Any examples?
>
> > > > Please notice the requirements:
>
> > > > 1) "name" and not ":name"
> > > > 2) no comma between "name" and "String" and "opt1" ...
>
> > > Almost certain this can't be done.
>
> > ok
>
> > > You could do something somewhat close to that, as seen in the below
> > example.
> > [...]
>
> > this is far to complex expressed.
>
> > Can you simplify this, e.g. avoiding usage of "rspec"?
>
> No, because the request itself makes me worried you'd actually use that
> code.

This is a public archived group, thus other readers will benefit from
a compact answer, too.

Of course I can try to minimize / summarize the code myself.

.

--
http://lazaridis