Thursday, August 30, 2007

>>flush vs. >>commit

I just learned that, in VisualWorks Smalltalk at least, if you send the message flush to an external stream (file, socket etc) this does not in fact flush unwritten content to the disk/socket. Rather it flushes unwritten content from the image down into the Smalltalk virtual machine.

If you really want to flush unwritten content, use commit instead.

Clear?

No comments: