1. New Standard Library Repository

I'm going to set up a repository at Sourceforge for a set of standard
include files for Euphoria. The initial set of files will include the
following:

   print.e      -- Boehme's v1.2 lib
   sprint.e     -- Boehme's/Lewis's v1.0 lib
   tbar_xpm.e   -- toolbar graphics from the Gnome project
   xpm_icon.e   -- Cuny's contribution of toolbar graphics
   series.e     -- Parnell's v1.0 lib
   ssl.e        -- Aku's Simple Standard Library of 2005
   stringhash.e -- Lewis' 2007 lib
   hlist.e      -- Babor's v1.0 hash lib
   hash.e       -- Parnell's hash lib

I think the licenses for all these libs allow placement in this repository.
But if you don't want your library included here, please let me know! I will
gladly respect your wishes. :)

If you know of a library (or more) that would fit well into this standard
repository, please let me know here or via email.

Basically, the files above are used in a few of the projects I'm actively
using and helping develop. I want them in a single repository to reduce
code duplication and increase development efficiency. Something like that.

I'm going to call the project the Wonderful Euphorepository of Standard
Functionality (or WESF). Just kidding. I don't know what I'll call it. So
suggest a name while you're thinking about what libraries should go there.

Now, these are ONE FILE libraries I'm talking about. Obviously win32lib
won't go in there, but ODBC.E might be a candidate, since it's just one file.

Anyway, please give me your suggestions. I will have something up on
Sourceforge by the end of this week... with or without you. :)

new topic     » topic index » view message » categorize

2. Re: New Standard Library Repository

c.k.lester wrote:
> 
> I'm going to set up a repository at Sourceforge for a set of standard
> include files for Euphoria. The initial set of files will include the
> following:
> 
>    print.e      -- Boehme's v1.2 lib
>    sprint.e     -- Boehme's/Lewis's v1.0 lib
>    tbar_xpm.e   -- toolbar graphics from the Gnome project
>    xpm_icon.e   -- Cuny's contribution of toolbar graphics
>    series.e     -- Parnell's v1.0 lib
>    ssl.e        -- Aku's Simple Standard Library of 2005
>    stringhash.e -- Lewis' 2007 lib
>    hlist.e      -- Babor's v1.0 hash lib
>    hash.e       -- Parnell's hash lib
> 
> I think the licenses for all these libs allow placement in this repository.
> But if you don't want your library included here, please let me know! I will
> gladly respect your wishes. :)
> 
> If you know of a library (or more) that would fit well into this standard
> repository, please let me know here or via email.
> 
> Basically, the files above are used in a few of the projects I'm actively
> using and helping develop. I want them in a single repository to reduce
> code duplication and increase development efficiency. Something like that.
> 
> I'm going to call the project the Wonderful Euphorepository of Standard
> Functionality (or WESF). Just kidding. I don't know what I'll call it. So
> suggest a name while you're thinking about what libraries should go there.
> 
> Now, these are ONE FILE libraries I'm talking about. Obviously win32lib
> won't go in there, but ODBC.E might be a candidate, since it's just one file.
> 
> Anyway, please give me your suggestions. I will have something up on
> Sourceforge by the end of this week... with or without you. :)

I think that this is a great idea, and kinda what I wanted the ESL to take the
last time we started one up. I wish you luck.

You would have to check with Juergen because I don't think it's an open license,
but what about lfn.e?

If I think of any others I'll be sure to chime in.

--
A complex system that works is invariably found to have evolved from a simple
system that works.
--John Gall's 15th law of Systemantics.

"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare

j.

new topic     » goto parent     » topic index » view message » categorize

3. Re: New Standard Library Repository

Jason Gade wrote:
> c.k.lester wrote:
> > The initial set of files will include the following:
> > 
> > <snip>

I think I'll also put the math.e lib(s) in there.

> I think that this is a great idea, and kinda what I wanted the ESL to
> take the last time we started one up. I wish you luck.

Unlike the prior efforts, this is really more of a repository of standard
includes. If you have any files from ESL, I'd be glad to look at them and
include them.

> You would have to check with Juergen because I don't think it's an
> open license, but what about lfn.e?

As long as it is cross platform... :)

But I could also split it up into platform-specific standard includes.
If you're developing on DOS, you'll want the Euphorepository for DOS, etc.

Thanks, Jason! :)

new topic     » goto parent     » topic index » view message » categorize

4. Re: New Standard Library Repository

c.k.lester wrote:
> 
> Jason Gade wrote:
> > c.k.lester wrote:
> > > The initial set of files will include the following:
> > > 
> > > <snip>
> 
> I think I'll also put the math.e lib(s) in there.
> 
> > I think that this is a great idea, and kinda what I wanted the ESL to
> > take the last time we started one up. I wish you luck.
> 
> Unlike the prior efforts, this is really more of a repository of standard
> includes. If you have any files from ESL, I'd be glad to look at them and
> include them.
> 

Check out http://oedoc.free.fr/Fichiers/ESL/ 

Now that find_from() and match_from() are in, locate.e may need to be thought
about again before including it I think. Otherwise, these files cover areas where
there's not much code available.

Some of the files have, at the end, a reference to esl_io.e. This was designed
so that extra printf() modifiers could be used without using specifically named
routines, and that may have not been possible at all in some cases (think of a
fraction between complex numbers). That part (2-3 lines at end of file) can be
removed if needed.

<snip/>
CChris

new topic     » goto parent     » topic index » view message » categorize

5. Re: New Standard Library Repository

c.k.lester wrote:
> 
> I'm going to set up a repository at Sourceforge for a set of standard
> include files for Euphoria. The initial set of files will include the
> following:
> 
>    print.e      -- Boehme's v1.2 lib
>    sprint.e     -- Boehme's/Lewis's v1.0 lib
>    tbar_xpm.e   -- toolbar graphics from the Gnome project
>    xpm_icon.e   -- Cuny's contribution of toolbar graphics
>    series.e     -- Parnell's v1.0 lib
>    ssl.e        -- Aku's Simple Standard Library of 2005
>    stringhash.e -- Lewis' 2007 lib
>    hlist.e      -- Babor's v1.0 hash lib
>    hash.e       -- Parnell's hash lib
> 
> I think the licenses for all these libs allow placement in this repository.
> But if you don't want your library included here, please let me know! I will
> gladly respect your wishes. :)
> 
> If you know of a library (or more) that would fit well into this standard
> repository, please let me know here or via email.
> 
> Basically, the files above are used in a few of the projects I'm actively
> using and helping develop. I want them in a single repository to reduce
> code duplication and increase development efficiency. Something like that.
> 
> I'm going to call the project the Wonderful Euphorepository of Standard
> Functionality (or WESF). Just kidding. I don't know what I'll call it. So
> suggest a name while you're thinking about what libraries should go there.
> 
> Now, these are ONE FILE libraries I'm talking about. Obviously win32lib
> won't go in there, but ODBC.E might be a candidate, since it's just one file.
> 
> Anyway, please give me your suggestions. I will have something up on
> Sourceforge by the end of this week... with or without you. :)

Hey CK:

I got an idea.

Why not setup a list of include text files names.

These files would be at first empty files with just names.

The files would be editable via a wiki and each user could add a

function that they considered important or needed.

After a period of time some time in the future these files would be

moved to a different area and become MASTER files that would not change. 

Bernie

My files in archive:
WMOTOR, XMOTOR, W32ENGIN, MIXEDLIB, EU_ENGIN, WIN32ERU, WIN32API 

Can be downloaded here:
http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan

new topic     » goto parent     » topic index » view message » categorize

6. Re: New Standard Library Repository

Bernie Ryan wrote:
> c.k.lester wrote:
> > I'm going to set up a repository at Sourceforge for a set of standard
> > include files for Euphoria. The initial set of files will include the
> > following:
> > 
> >    print.e      -- Boehme's v1.2 lib
> >    sprint.e     -- Boehme's/Lewis's v1.0 lib
> >    tbar_xpm.e   -- toolbar graphics from the Gnome project
> >    xpm_icon.e   -- Cuny's contribution of toolbar graphics
> >    series.e     -- Parnell's v1.0 lib
> >    ssl.e        -- Aku's Simple Standard Library of 2005
> >    stringhash.e -- Lewis' 2007 lib
> >    hlist.e      -- Babor's v1.0 hash lib
> >    hash.e       -- Parnell's hash lib

More files to be included in initial repository:

    math.e
    compare.e
    stats.e
    sets.e

I'll take suggestions for modifications to these files in the Sourceforge
forums for the project. Matt, doesn't Sourceforge allow a wiki? Bernie,
your idea is reasonable, I just don't want to take the time to manage it.
It's the "after a period of time" I want to avoid. :)

new topic     » goto parent     » topic index » view message » categorize

7. Re: New Standard Library Repository

Bernie Ryan wrote:
> 
> I got an idea.
> Why not setup a list of include text files names.
> These files would be at first empty files with just names.
> The files would be editable via a wiki and each user could add a
> function that they considered important or needed.
> After a period of time some time in the future these files would be
> moved to a different area and become MASTER files that would not change. 

That's an interesting idea, and probably worth pursuing, however, it 
wouldn't serve the CK's purpose.  He's been getting involved with most 
of the projects that I've started over the years.  There are several files
(which he mentioned) that make repeat appearances in these projects, and
there are already dependencies between projects, leading to duplicate files,
and the namespace resolution hassles that follow.

Each project has its own svn repository on sourceforge, so many of these 
files have been duplicated, which is not so great.  It hasn't been that
big of an issue (though definitely an annoyance, and occasional configuration
management problem), but now that I'm not the only developer, it makes sense
to pull them out into a single repository.

They're not really meant to become some sort of official standard, although
since I use them all the time, I wouldn't complain if they did. :)

Matt

new topic     » goto parent     » topic index » view message » categorize

8. Re: New Standard Library Repository

c.k.lester wrote:
> 
> I'll take suggestions for modifications to these files in the Sourceforge
> forums for the project. Matt, doesn't Sourceforge allow a wiki? Bernie,
> your idea is reasonable, I just don't want to take the time to manage it.
> It's the "after a period of time" I want to avoid. :)

Yes, I believe that the project admin has to enable it and set permissions,
etc.  I don't think anyone but me has done anything with it, but I've got
a wxEuphoria wiki:

http://wxeuphoria.wiki.sourceforge.net/

Matt

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu