Le 30/6/15 11:20, Marcus Denker a ��crit��:

On 30 Jun 2015, at 11:16, Guillermo Polito <guillermopolito@gmail.com> wrote:

Another detail is that LinkedList's design is heavily tied to the VM. Our linked list implementation can contain any object that *looks like a link*, meaning��
- in the higher level they have to understand the message nextLink and nextLink:
- in the lower level, if it is a linked list used by the VM, the nextLink should be the first inst var of the object.

What I mean with this is that we should be careful when changing linked list. Changing its internal representation may crash your image ^^.


We should really rename it to ���ProcessList��� and put a comment ���do not touch!!!���, then make a copy and have a Linked List that we can change���
there are many issue tracker entries related to the linked list, as people try to use it but nobody dares to change it.

I reimplemented it once.
Now I was just consider Stack implementation.

Marcus