OpenEuphoria

Re: Euphoria 3.2 compatibility

• Posted by CChris <christian.cuvier at agricult?re.gouv?fr> Apr 24, 2008
• 662 views

OtterDad wrote:
> 
> Jeremy Cowgar wrote:
> > Yes, undoubtedly, *any* new function added to Euphoria either core or
> > include/???.e
> > *will* cause code to break. 
> 
> at the risk of being flamed to death, please see my previous reply which
> relates
> to upgrades and code breaking:
> 
> <a
> href="http://www.openeuphoria.org/cgi-bin/esearch.exu?fromMonth=8&fromYear=C&toMonth=8&toYear=C&postedBy=otterdad&keywords=frozen+language+versions">http://www.openeuphoria.org/cgi-bin/esearch.exu?fromMonth=8&fromYear=C&toMonth=8&toYear=C&postedBy=otterdad&keywords=frozen+language+versions</a>
> 
> or this entire thread:
> <a
> href="http://www.openeuphoria.org/cgi-bin/esearch.exu?thread=1&fromMonth=7&fromYear=C&toMonth=9&toYear=C&keywords=">http://www.openeuphoria.org/cgi-bin/esearch.exu?thread=1&fromMonth=7&fromYear=C&toMonth=9&toYear=C&keywords=</a>"Frozen+language+versions"
> 
> <now dons fire retardant clothes>
> 
> Yours, OtterDad
> 
> Don't sweat it -- it's not real life. It's only ones and zeroes. Gene Spafford

I can't remember who also wrote on this subject of legacy code and language
stability. His strategy was to catalog exactly which version of which include,
and which Eu version, each of his Eu apps used. In thatt way h said he was able
to fully test any upgrade before proceeding to it, and to avoid surprises.

Why not simply do that, and let the alive community add or enhance whatever
exists? A lot of little things in Eu have been made overly simplistic, and the
test of time has shown this was usually a liability, leading to either changes
(value() now returns a 3 element sequence) or new routines (like find_from() from
find()).

CChris