[ANSI-Smalltalk] what to work on first

[Esteban A. Maringolo]

On Nov 16, 2007 10:40 AM, John O'Keefe <wembley.instantiations at gmail.com> wrote:
> I agree that files, sockets, (and streams since they relate strongly
> to both) are a good starting point for the next revision of the
> standard.
>
> One way to judge what we should work on first is to ask cross-dialect
> feature developers what gives them the most pain.  What areas of
> standardization would make Seaside, Glorp, Aida, Refactoring Browser,
> Toothpick, etc. easier to port?

For Seaside the Date standarization is required, because it uses it a lot.
If you want to have a fully functional seaside (as is in Squeak) you
have to port the Chronology package too.

For Swazoo the Socket part is tricky, because the Sport portability
layer defines only one class of socket, whereas Dolphin defines one
for Server (listener) and other for client and established
connections. Some options of the socket should be considered also,
i.e. setsockop() has no meaning in a windows implementation, so the
options should be the common denominator or modularized.
And the socket standarization should also consider the option of
implementing UDP sockets, not only TCP.

Regards,

-- 
Esteban A. Maringolo
eMaringolo at gmail.com