I still say that max's memory mangement is insane.

BlitzMax Forums/BlitzMax Programming/I still say that max's memory mangement is insane.

In what way is my design poor?
You are using a data structure that is unsuitable for the problem you're trying to solve.

If I make a list of points, and I want to iterate through them, For EachIn works fine UNTIL I need to access the previous or next point in the list while I am on the current point.
I've already explained to you how you can avoid that. If you chose to ignore it, I'm having a hard time seeing why I should feel sorry for you.

If I don't use _Link, then I have to do this everywhere I need to have a loop:
Or you could override the iterator to return links, if you *need* them, rather than the actual objects.

ometimes you need to have a list of objects AND know the link that contains a particular object
Talk about attacking every problem as if it where a nail. If you need a collection, and you need to be able to iterate over them in linear time, and remove them in constant time (or better than linear time), then you are using the wrong collection! Try an associative array instead, like TMap (log n) or that hashMap (near-constant) that's floating around here somewhere.

You know just making one simple change to Max would have made my life a lot simpler by rediucing the number of cycliuc references
As I've already explained, you can make that change yourself, if the default behavior doesn't suit you. As I've also already explained, this does not nessecarilly involve changing the core BMX modules.