Just wondering if this was intentional, or if it is a potential issue:
In most cases, entity 0 is reserved for system resources. For example, bitmap 0 is the system's drawing screen. Therefore, "Create Bitmap 0,256,256" is not allowed. All, or at least most, other entity types (images, memblocks, objects, etc.) have this same restriction regardless if entity 0 is used by the system. For example, [I am pretty sure] object 0 is not really a system resource.
However,...
R = Make Vector3(0)
...seems to work just fine. While this might be good news (Woohoo! We can use
all of the 2^32 vectors!
), I am concerned that perhaps this was really done in error instead of intentionally. For example, will some of the 107 vector command(s) / function(s) give an error if vector 0 is used? Or perhaps there will be some less obvious error, such as the system deciding it needs to use its vector resource and overwrites the data in vector 0.
The reason I am asking is that I am writing some error-catching functions to ensure entities are valid before using them for other functions. Should these error-catching functions not allow vector 0 just to be safe? Or is vector 0 completely 100% golden-safe to use?
From a curiosity perspective, if this was intentional - why not allow other entities to use 0 such as objects? One possible reason might be that, "object 0, even if not used by the system today, may one day be used by the system in a later update to DBPro." However, this reasoning is equally applicable to vectors. Are all the other entity-zeros used by the system, but not vectors?
