From: Josh Cheek <josh.cheek@...>
Date: 2011-06-01T17:28:07+09:00
Subject: Re: CORE - Specialized Attribute Definition

--90e6ba4fc1c0ac055a04a4a24cc8
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: quoted-printable

2011/6/1 Ilias Lazaridis <ilias@lazaridis.com>

> On 31 =CC=DC=FA=EF=F2, 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"?
>
> .
>
> --
> http://lazaridis.com
>
>
No, because the request itself makes me worried you'd actually use that
code.

--90e6ba4fc1c0ac055a04a4a24cc8--