OpenEuphoria

RE: private include files

• Posted by irv mullins <irvm at ellijay.com> Oct 15, 2004
• 486 views

Chris Bensler wrote:
> 
> 
> OtterDad wrote:

> Even if the language is backwards compatible, the libraries you use are 
> not always, you still have the same problem.
> The fact that compatability should be broken is not something that 
> should be considered lightly, I agree. But if the benefit of the changes 
> made will outwiegh the detriment of breaking code, then it should be 
> done.

Compatability with 'old' code is only somewhat important. How often have 
you written a new version of some program in another language altogether?

I've done so dozens of times, because my first choice of language proved 
to be less-than-optimal. In some cases, the task outgrew the language. 
In others, I discovered a much easier/cleaner/faster or otherwise more 
productive way to accomplish the job. 

I'm certain other programmers have done the same thing. So if changing 
languages totally isn't a hindrance, then how can one or two small changes 
be all that big of a burden?

> When there are serious flaws in your plan, you will correct them, won't 
> you? Or you just keep pushing on like a good little steam engine, and 
> hope that things don't fall apart before you finish?

Or, just hire some PR droids to divert attention from the flaws, while 
hoping you can cash out before things fall apart. I think that's called 
the Redmond Way.

Irv