Posted by Esteban A. Maringolo-2 on Jan 13, 2005; 3:40pm
URL: https://forum.world.st/become-and-oneWayBecome-tp3372645p3372668.html

DiegoC escribió:
> Debugging can gets more difficult; workspaces, inspectors and open views
> could show you confusing information.

It's true, i've had many crashes until it got stable.
Now it's stable. And when I open an inspector, it becomes the real
object and inspects the object or nil.

For example, i was missing the the forward of the first message
(which caused the become), and my objects didn't respond  until the
second send :-D

 > I'am not saying to avoid it use,
> just to be carefull and consider that in most cases you can solve the same
> wrapping your objects inside others and reference those ones.

Yes... indeed I did wrapping/proxying for objects* external to the
smalltalk.

* when i say objects I refer to true objects outside, not to
persisted data (which is the actual case).

 > For example
> I've seen desings where anInvoice becomes aReceipt, and things like that.
> I've found that most times you get better designs without become.

wow, that's ugly, and it's not the case.
Because it doesn't affect the operation of my domain objects and
rules. It's just the object between a living ambiance (the
smalltalk), and the persistence system.

> On the other I was impressed by the perfomance of Dolphin's #become:
> implementation, and also I admit I've used in a real systems.

I've didn't tested it. If I have time I would benchmark it (knowing
how, of course :-) ).

Best regards.

--
Esteban A. Maringolo
[hidden email]