Any problem using udpated/changed pattern with component

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Any problem using udpated/changed pattern with component

Hilaire Fernandes-4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I want one component to be informed from another one when the latter
attributes changed.

Are there any problem using udpated/changed pattern with components?

I am wondering about side effect as components still referenced in
memory even if not used anymore.


Hilaire
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ9XW1SAvrR6lz6PQRAphWAJ9UgpzpyqGjb/JtJV6jLEzUPdZpowCgtrUc
zlNmgSBvNJ/fUHdHZcuUZ1g=
=3rB4
-----END PGP SIGNATURE-----

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Any problem using udpated/changed pattern with component

Philippe Marschall
Components are Smalltalk objects so Smalltalk object semantics for
memory management apply.

Cheers
Philippe

2009/4/27 Hilaire Fernandes <[hidden email]>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I want one component to be informed from another one when the latter
> attributes changed.
>
> Are there any problem using udpated/changed pattern with components?
>
> I am wondering about side effect as components still referenced in
> memory even if not used anymore.
>
>
> Hilaire
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFJ9XW1SAvrR6lz6PQRAphWAJ9UgpzpyqGjb/JtJV6jLEzUPdZpowCgtrUc
> zlNmgSBvNJ/fUHdHZcuUZ1g=
> =3rB4
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Any problem using udpated/changed pattern with component

Hilaire Fernandes-4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So as long as it is reliably use, it is not a problem...

Being a C++ freak, I always have hight doubt and fear with GC.
Kind of "too good to be true" fear :)

Thanks

Hilaire

Philippe Marschall a écrit :
> Components are Smalltalk objects so Smalltalk object semantics for
> memory management apply.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ9ad5SAvrR6lz6PQRAsAIAJ9bm5i55LLrhPF9dVitnF5WyAdp/wCeLnfM
G6qMHFiE6k/QC6WOcjsZn9s=
=hHrC
-----END PGP SIGNATURE-----

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside