[Openmcl-devel] MCL no longer on features?

[Gary King]

Thanks Gary,

I agree with your reasoning... Software is often treated as if it was  
less flexible than hardware and that causes far more headaches than  
it saves in the long run. I missed the Sept. e-mail but have no  
strong opinions regarding the 1.1 or 1.2 issue (FWIW <smile>).

On Feb 14, 2006, at 7:50 PM, Gary Byers wrote:

> I think that if some code is broken now (#+MCL no longer implies
> OpenMCL), it's best in the long run.  The change does need to
> be better publicized than it has been, and if people think that
> it's too disruptive and not worthwhile to make the change in the
> next release that's seems like a reasonable argument.  (I don't
> think that the 1.0 release notes mentioned this; maybe it'd be
> best to schedule the change for 1.2 and mention the issue in the
> 1.1 release notes.)


-- 
Gary Warren King
metabang.com
http://www.metabang.com/