Re: Euphoria will be Free and Open Source!
Vincent wrote:
>
> Kat wrote:
>
> > You are not *required* to use Matt's objects, and you can still
> > program in a procedural fashion. It's like "goto", don't use it if you
> > don't want to!
>
> Wouldn't that depend on the libraries I use within my programs? What if I
> needed
> to use an Eu library but was written in an OO way? I would likely need to use
> a OO programming style to interface with it, correct?
>
> In that case, I would be required to program in that style or re-invent the
> wheel by creating a procedural style library. But since I dont understand
> object
> oriented concepts (no matter how hard I to learn) I wouldnt be able port the
> library.
Not necessarily. OOEU currently has the ability to preprocess code that
uses the OO features of OOEU into standard RDS Euphoria. Basically, all
the OO stuff is implemented in the front end, and only outputs standard
Euphoria IL code. The names look a little messier, since you get to see
the name decoration (which uses a pretty simple scheme, BTW). I suspect
that I'd keep this feature to maintain easier compatibility with other
Euphoria implementations.
In any case, the OO aspects of OOEU are somewhat limited. There are no
virtual functions, for instance (which some purists would say make OOEU
not really OO). Perhaps the greatest benefit is that it allows you to
use more complex, defined data structures in the place of sequences with
constants defined as accessors. And I think that if I were to add getters
and setters, you could have a more seamless use of memory structures.
Matt Lewis
|
Not Categorized, Please Help
|
|
