Re: Compiler messages

No, but writing something with no plan for getting it used might be a
good way to start one.  Too many people have written too much fine code,
only to see it lost because people cannot agree on a direction for
Squeak.  I am happy to make some small changes and share them here, or
do a more elaborate job for wider consumption.  Writing something highly
involved only to watch it fall into the NIMBY black hole?  No, thanks.

Bill




Wilhelm K. Schwab, Ph.D.
University of Florida
Department of Anesthesiology
PO Box 100254
Gainesville, FL 32610-0254

Email: bschwab@...
Tel: (352) 846-1285
FAX: (352) 392-7029

>>> tim@... 11/11/07 6:57 PM >>>

On 11-Nov-07, at 3:01 PM, Bill Schwab wrote:

> Tim,
>
> Ok, then what do we do?  Distribute it as a group development, or try
> for inclusion in the mainstream?
Well the first thing is to Just DoIt. If it existed and was well  
written and passed sensible tests then I don't think it would be too  
difficult to persuade whoever is/was the release team to incorporate it.

Worrying about how to handle something that doesn't exits yet is a  
sure recipe for ulcers.

tim
--
tim Rowledge; tim@...; http://www.rowledge.org/tim
Strange OpCodes: PSM: Print and SMear


_______________________________________________
UI mailing list
UI@...
http://lists.squeakfoundation.org/mailman/listinfo/ui

_______________________________________________
UI mailing list
UI@...
http://lists.squeakfoundation.org/mailman/listinfo/ui