[Pharo-project] How removing a class can broke DataStream/ReferenceStream/SmartRefStream

Mariano Martinez Peck marianopeck at gmail.com
Sat Oct 23 16:08:44 EDT 2010


Pharo core version: 12210

In Pharo 1.2, the class SoundBuffer was removed.
 DataStream >> initilize
was modified, and just added an Smalltalk at: ifPresent: for such class.
However, this broke DataStream and all its subclasses.

This is because DataStream is chryptic, impossible to understand, and
impossible to change.

The changed affected when trying to write compiled methods (just by
chance, because they were after in the list, of SoundBuffer).

I've spent 3 hours to fix this bug grrrrr



Fix in Inbox:

Name: SLICE-Issue-3147-RomovingSoundBufferBrokeDataStream-MarianoMartinezPeck.1
Author: MarianoMartinezPeck
Time: 23 October 2010, 10:07:35 pm
UUID: c4f1cf01-b8b8-471d-b3c2-e67bdf08d8e5
Ancestors:
Dependencies: System-Object Storage-MarianoMartinezPeck.112

Fix to issue 3147 <http://code.google.com/p/pharo/issues/detail?id=3147>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20101023/c94db765/attachment-0001.html>


More information about the Pharo-dev mailing list