1. RE: Eu Rebellion (was: New Euphoria Users Website)
> From: Kat [mailto:kat at kogeijin.com]
> I don't think i asked for pass-by-reference, i had asked for variable
> creation
> and knowing what vars there are, which is more of an
> associated-list sorta
> animal. I didn't know you had a crash routine, i didn't know
> you had a new
> interpreter out until i searched the archives by "Lewis"!
No, the pass by reference was really a side effect of the dynamic creation.
My announcement (not terribly blaring, I admit) must have been lost in the
message traffic. :)
> Re the DDE package, i did ask for it, but i can't use it, i get this:
> D:\Euphoria\dde\dde.ew:10
> registerw32Function has not been declared
> DdeInitialize = registerw32Function( user32, "DdeInitializeA",
Hmmm. That's a win32lib call. I'm kinda surprised I used that (been a
while). Are you running an older win32lib? In any case, you could safely
change those to define_c_func, as long as you also use open_dll to get the
handle to user32.
> Programs in the archives that fail to run are common.
Yes, and unfortunately some of them are mine sometimes. I often get emails
from people asking for help when one of my libs doesn't run. Since I've
been doing some sorta weird stuff, its often because people don't have
everything they need installed. In any case, I appreciate when people have
taken the time to try my stuff and ask me why it doesn't work. I usually
get back to them pretty quickly with a solution.
> Er,, if you use EDS, which i don't, because i didn't know i
> could get a list of the vars in it *while running*. Your's lists
> when it crashes. Which is nice, but on a database that fills the
> harddrive, getting a var dump after a crash is a bad thing.
True, and then you wouldn't want to use the routine as provided. It was
merely a general solution for the problem, since I can't know what variables
any app will have, etc. It should be fairly easy to tailor to individual
needs, and eds was sort of an obvious solution, especially since that's what
someone else had asked for.
And, yes, perhaps I wasn't clear about when you could get a list of vars:
any time. I just did the obvious and combined the crash routine and dynamic
access to vars to do a dump.
> > IMO, this is a very valid reason for splitting from the main list,
> > and might be very useful--to us and to Rob.
>
> Not to Rob, that's the reason people are leaving.
I disagree. We tend to lose people because the pace of change is so slow.
Rob does add things based on user input--just not everything and at a pace
that many would like. However, if we produced working interpreters that we
all found useful, we might be able to demonstrate the utility and
effectiveness of the changes, plus giving Rob a leg up on the official
implementation. I think this is perhaps the closest Eu will come to a true
Open Source language. Rob's still in control, but there's a lot more energy
and creativity being focused where it can do the most (at least as far as
changing the language is concerned).
Matt Lewis
2. RE: Eu Rebellion (was: New Euphoria Users Website)
I like the idea of an open-source EXU. So long as the folks who work on
it haven't seen Rob's code (or maybe even if they have, if Rob OKs it),
there wouldn't be any copyright violations, and I don't think Rob has
any patents on his code. I, for one, have been champing at the bit to
port EU to CYGWIN, a U**X-y port of the FSF tools to WinX platforms, but
with a layoff in the offing and no raise this year, I can't scratch
together the bucks for the source. Doing the entire job by oneself is
daunting, but as the open-source community has discovered, many coding
hands makes for lighter work for all. Better yet, if the 'maintainer'
gets tired of the job, he can always hand it off to somebody else; best
of all, as with any open-source project, anybody could maintain his own
personal version. Are you putting together an open-source effort?
thx, phil long
jbrown105 at speedymail.org wrote:
> On 0, "C. K. Lester" <cklester at yahoo.com> wrote:
> >
> > > Despite all the GUI toolkits, Euphoria is still a DOS application.
> > Anything
> > > extention beyond that has been developed by the users, and isn't
> > officially
> > > supported by RDS.
> >
> > As such, why concern ourselves what will be "supported" by RDS? Let's
> > start
> > a EUPHORIA Users Group that will build on the core provided by RDS. Who
> > cares what RobC will "support" or not? We're just using him for his core
> > language. :)
> >
> > There are groups who do the same with Java, VB, Python, Puka, Lua,
> > LiverNuts, etc...
> >
> > > I'm not saying this is a bad thing. That's just the way it is, and I
> > > don't
> > see
> > > any reason to think it will change in the near future.
> >
> > RDS won't change it, but what stops a group of brilliant developers from
> > taking things as far as possible?
> >
> > Or is the core of EUPHORIA just too limiting? Or are there different
> > roadblocks?
> >
>
> This was the idea behind Dredge. Exu was the core, and then the parsers
> would
> build on top of it. However, this didn't inspire a lot of people,
> apparently,
> so I've decided it may be time to put it on the back burner.
>
> Instead, I'm gonna try to move to an open-source Exu. Perhaps this might
> inspire more people?
>
> jbrown
>
>
> --
>
>
3. RE: Eu Rebellion (was: New Euphoria Users Website)
phil long wrote:
[snip]
>I, for one, have been champing at the bit to
> port EU to CYGWIN
[snip]
I don't understand Phil ... why not just use ex.exe or exw.exe???
Cygwin is a POSIX layer on top of Windows.
Why port exu to Windows when exw.exe already exists?
What benefit is there?
Regards,
Ray Smith
http://rays-web.com
