regular (non-shared) objects, using the New object command. These objects can be edited without any specific access control but cannot be shared between processes.
I am a bit confused by this statement in the documentation.
In the past the scope of an object was determined by the type of variable the object was placed into (local/process/interprocess). We used objects extensively (local/Interprocess) types.
If what is stated here in the manual were true (then a lot of my code would break).
Therefore I did test methods with (local/process/Interprocess) object variables. The scope of the object variables was as it has been, so no change in the behavior.
I therefore think that it would appropriate in the documentation to explain this in more detail so that people will get a full explanation of scope of an object variable.
If there is a reason for not explaining this (ie. upcoming change in behavior) this would be important to know. If all my interprocess object variables if not declared as shared Objects will now not be available to other processes that would be a huge change in the behavior of 4D.
Thank you for the decades of great 4D Documentation.
Enter your comment here:
Regular or shared object
You can create two types of objects:
regular (non-shared) objects, using the New object command. These objects can be edited without any specific access control but cannot be shared between processes.
I am a bit confused by this statement in the documentation.
In the past the scope of an object was determined by the type of variable the object was placed into (local/process/interprocess). We used objects extensively (local/Interprocess) types.
If what is stated here in the manual were true (then a lot of my code would break).
Therefore I did test methods with (local/process/Interprocess) object variables. The scope of the object variables was as it has been, so no change in the behavior.
I therefore think that it would appropriate in the documentation to explain this in more detail so that people will get a full explanation of scope of an object variable.
If there is a reason for not explaining this (ie. upcoming change in behavior) this would be important to know. If all my interprocess object variables if not declared as shared Objects will now not be available to other processes that would be a huge change in the behavior of 4D.
Thank you for the decades of great 4D Documentation.
Jody Bevan