[Ash.]

Quote:

Originally Posted by ****** Nice simple release with useful functions, but I have two questions: 1) Why PVars? Your system does not stream checkpoints so there is a finite number of checkpoints, bounded by the number of players which is known at compile time. PVars are useful for instances where the memory requirements can't be known in advance, which is not the case here.

PVars: simply because there can only be only one single checkpoint location at any given time. However i see your point now; I may modify it. However, with PVars; the user could request the information at any point in any script without necessarily including the "CP" include (however it would be needed somewhere, obviously)

Quote:

Originally Posted by ****** 2) Why "__x" and "__size" etc, not "x" and "size"? It is not a rule, but symbols starting with underscores are often reserved for framework internal code and symbols starting with double underscores for symbols defined by the compiler itself. This is not the case here but you may want to bear it in mind for the future - the idea is to try and reduce the chance of a symbol name collision.

I actually didn't know that; I thought by using underscores I was reducing the chance of clashing names! There are no name clashes here though, and so i won't worry about it too much. I'll look out for that in the future though.

Thanks,
Ash