1. RE: ESL project
> > [Switch topic]
> > ESL project. Yeah. I'm kind of working on stuff, basically
> filesys.e right
> > now and maybe seqops.e (sequence operations) in the near
> future. I don't
> > think ESL has any specifications for CGI-type stuff and I
> certainly don't
> > know anything about it. So, I don't know.
> >
> > If it wasn't for Jeremy Peterson I think the ESL project
> would be about
> > dead. I'm taking his code as a basic blueprint and
> re-creating it to fit my
> > own ideas. Hopefully the rest of the team will accept my
> code once I release
> > it, or else I'll just release it on its own.
> >
> > --
> > "Any programming problem can be solved by adding a level of
> indirection."
> > --anonymous
> > "Any performance problem can be solved by removing a level
> of indirection."
> > --M. Haertel
> > j.
> >
> > ------------------------------
> >
> > Visit oedoc.free.fr/Fichiers/ESL/
>
> Okay, I will. I thought you were going to be out of town for
> the month? 
These were the pans, but that will happen perhaps between 03/10 and 04/02 or
something. Not sure yet at this point.
Good to recover the "replied-to" marks :).
>
> Once I get something that I like, I will be sure to submit it
> for discussion before doing anything else with it.
>
> >
> > I still have files there instead of Sourceforge because some issues
> > regarding documentation guidelines and overall design were
> not yet clear.
> > From my understanding, they still aren't, but there's no
> wish to establish
> > standards in this respect.
> > Part of the problem could be that some of the central
> activities of the
> > project, like code and doc reviewing, didn't start yet. Any
> thoughts, Derek
> > N.?
>
> I know this should be on the ESL list instead of here, but I
> only check that every few days. Whereas here, I'm constantly
> hitting that refresh button!
>
> I have some documenting questions but I'll worry about them
> as I write the comments and code. Since the documentation is
> part of the code, I'll get clarification when I submit
> something for review.
>
> >
> > Not all modules are implemented there, and some extras are
> available too.
>
> It's not perfect, but as I've probably said a hundred times
> now I think that Jeremy Peterson's esl0.01 is the best start
> we have yet.
As I may have said, this code has a terrible drawback, which is that it does
nothing useful. For any programming purpose, you have to enhance these basic
tools and eventually rewrite them. Not enough options, no flexibility nor
ability to combine the tools. The aim, as I understood, of the ESL is to
_avoid_ such perpetual rewrites.
esl0.01.zip is certainly an interesting, useful demo for Euphoria,
definitely not a set of tools for productive programming.
Ok, this has to be discussed on the ESL mailing list, for sure.
> Between that code, the ESL website, glibc and
> msvcrt documentation, and my own ideas that I need to write
> down, I think we've got something to start with. When I have
> some code that is ready for reviewing, I'll submit it for review.
>
CChris
