Re: Class Constants - pros and cons
Alan Gutierrez wrote:
The scenario under discussion is, I want to do something that will reach
the limits of system memory. Your solution is procure memory. My
solution is to use virtual memory.
Again, it seems to me that `MappedByteBuffer` and a bunch of little
facades to the contents of the `MappedByteBuffer` is a preferred
solution that respects memory usage. The design is as expandable,
easy-to-maintain and bug free as a great big array of objects, without
having to think much about memory management at all.
I like that idea.
I don't know where "parallel" arrays come into play in the problem
Did you read this thread? Like, say, yesterday, when Tom McGlynn wrote:
E.g., suppose I were running a simulation of galaxy mergers
of two 100-million-star galaxies. Stars differ only in position,
velocity and mass. Rather than creating 200 million Star objects
I might create a combination flyweight/singleton Star where each
method call includes an index that is used to find the mutable
state in a few external arrays.
Alan Gutierrez wrote:
described. I'm imagining that, if the records consist entirely of
numeric values, that you can treat them as fixed length records.
--
Lew