#include

[Foz]

I definitely appreciate the callFunction() function. I understand it is a recent addition to EFS and am thankful to whoever added it.

I want more though... I wish there were a way to include functions from another file so they could be called as easily as if the functions were defined in the same efs file. For example, I have a sign() function that tells me if a number is positive or negative. If the sign() definition is in the same file I can call this function as sign(x), but if I put the definition in another file, then I have to call the function as callFunction("/bin/utilities.efs", "sign", x) — quite awkward. Does anyone know of a way to be able to just say sign(x) if sign() is defined in another efs file? Or could an include directive be an improvement to a future version of EFS?

[gspiker]

Hi Foz,

This isn't possible at this time.

At one time I was talking to the developers about allowing an EFS to add functions that would appear as if they were part of the EFS language. The idea is that such EFS would be loaded on eSignal startup and the functions would be treated as a keyword by the editor, callable by all EFS etc. There were some major potential issues this raised, that we were never able to determine a good method of eliminating, despite some serious back and forth. CallFunction() was the work around.

I'm not sure what may happen in the future, but for now Call Function is all we have.

Garth