Michael Donegan writes:
 > Squeak is great, but it has a few pitfalls when you actually try to get
 > something done. PositionableStream>>nextNumber: and nextInt32 have similar
 > problems with
 > missing asInteger after a self next.

I think this is a bit harsh.

In the case you mention, these methods are intended for streams of
bytes, not streams of characters.  If you send "binary" to the stream
before calling them, or otherwise use a stream of bytes, then they
work fine.

For the original poster's case, the failing methods shouldn't fail,
but then again they aren't really needed, either.  If you look at
FileStream's methods, you can actually open the file in whatever mode
you want anyway, and thus not have to change the mode afterwards.


In general, Squeak does have rough spots.  But at least in Squeak you
can *change* the things you don't like.  This isn't true for all that
many development environments.  And furthermore, really bad problems
don't tend to last for long, because someone among the community will
fix it and publish their fix.

Lex