Re: Eu improvements (Part 1)
c.k.lester wrote:
>
> Matt Lewis wrote:
> >
> > Well, the ooeu equivalent is:
>
> Does ooeu perform comparably to standard ex(wcu).exe? Is it cross platform?
> If ooeu does everything ex... does, with just a little more overhead,
> then I might consider sending it to our testing workshop.
Most of the OOP stuff is completely front end related. It's probably a
little slower to parse, but I doubt it would be easy to tell the
difference (haven't done a lot of tests). There are several things that
I have modified in the C-based backend that might cause slight slowdowns in
certain cases.
Overall, though, it should be very similar, since it's largely the same
code. It's cross platform (although I don't do any DOS stuff, you could
probably build it there if you really wanted to--same for BSD). The
last release was before the open sourcing of eu, so that's all based on
the euphoria implementation.
I haven't gotten all the ooeu features working with the c-based backend
yet. The eval() features are pretty much the only things I can think
of off the top of my head--that's a much more complex implementation,
because you have to re-bridge the frontend to backend gap (converting all
the indices to pointers, etc). My approach is going to be to create
linked lists of things like the SymTab and the __eval__ code blocks
that will grow and change each time there's an eval.
It's all up on svn at sourceforge (ooeu.sf.net), including makefiles
for OpenWatcom and gcc.
Matt
|
Not Categorized, Please Help
|
|
