OpenEuphoria

Re: Euphoria 3.2 compatibility

• Posted by Bernie Ryan <xotron at bl??frog.com> Apr 24, 2008
• 688 views

OtterDad wrote:
> 
> CChris wrote:
> > His strategy was to catalog exactly which version of which include,
> > and which Eu version, each of his Eu apps used. <snip> Why not simply 
> > do that, and let the alive community add or enhance whatever exists?
> 
> I actually do that today. I store a copy of every included file and the 
> entire bin directory used on every deployment. It bloats simple 20k exw 
> files into 10 Meg deployment archives, but adds an invaluable stability 
> layer that helps me sleep at night.
> 
> Yours, OtterDad
> 
> Don't sweat it -- it's not real life. It's only ones and zeroes. Gene
> >Spafford


OtterDad and others:

    This is what I think should happen.

    Stop adding features on up to 3.2.

    Start a NEW Version of Euphoria 4.0 and do all the changing you

    want; create new standard libraries but these will only be used

    by 4.0.

    This doesn't break any older code in the library if a person uses

    version 3.2.

    Then after the users get familiar with version 4.0 and iron out the

    bugs. The older archive programs can be gradualy rewritten to

    operate in version 4.0.

    Doing things the way they are now is stupid, people are running around

    to add new features while the other user's are trying to keep older

    code functioning with changes.


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