On 24-08-2008 03:26:25 +0200, Romulo Goncalves wrote:
Modified Files: remote.mx Log Message: Redo remote.mx to no longer have externally visible functions that are only for internal use. Also minimise the number of messages a bit. remote now assumes a strict typed scenario, meaning remote.get will require the variable to assign to to be typed. But how bpm will compile with these changes? I am calling these functions there...
ok I saw the bug opened by Sjoerd...
The code will be moved and corrected once I am back, but in the mean time I do not see a reason to not have this functions available for external use. In this moment I define a mal command (e.g) in the bpm module to call internal functions from remote.mx.
Internal functions do not check arguments and expect some proper call order, etc. Even /if/ it were a good idea to call them from another file, they should be changed/wrapped to do the required pre- and post-checks. Also, I didn't expect internal functions to be used externally, which lead to this problem. The implementation now changed, but the external API hasn't been changed.
The future plan is to change the bpm optimizer to detect a mal command (eg. send) and re-write the mal command by the necessary remote commands. But until there I will use the internal call of remote functions.
I looked at the functions you have, and guessed that you could also implement those as MAL functions, but Martin even thought that the "future" could be more or less "tomorrow" (or "next week").