SMACC and Version 4
Doug Way
dway at mailcan.com
Thu Apr 15 04:27:26 UTC 2004
On Tuesday, April 13, 2004, at 05:45 PM, Dan Ingalls wrote:
> For the most part, we anticipate the changes underlying Version 4 to
> be invisible to the average user. However, one change has come up
> that extends into a number of adjacent areas, so I want at least to
> warn everyone of its coming.
>
> The change is to replace our barnacled old ST-80 compiler with a shiny
> new SMACC-based compiler.
> <snip>
>
> There will be a number of upsides to this move, not the least of which
> is the introduction of Anthony's closure support soon thereafter, with
> accompanying VM support to follow soon as well.
>
> If anyone knows a reason why not to make this move, please speak now
> or forever hold your peace.
Sounds great to me.
This is sort of a tangent, but on the subject of SmaCC:
Because SmaCC is MIT-licensed, as we make any changes to the SmaCC
package (as part of Version 4 or anything else), we should keep the
original MIT-licensed SmaCC package as-is, and have a separate SqueakL
licensed package for Squeak related changes. This is also true for
SUnit, which is the only other non-SqueakL package in the base release.
- Doug
More information about the Squeak-dev
mailing list
|