#58 Code inclusion rework

Closed
opened 9 months ago by belliash · 1 comments

Actually, we got 2 builtin function: include() and require(). Both of them are available only inside methods body. The proposition is to:

  • make ‘require’ available only on the global scope in order to include source files containing classes.
  • make ‘include()’ available only inside methods body, to include a part of code that will be executed during method call. Such code should be a valid AerScript code that can be executed inside method body (just like using ‘eval()')

Thus ‘include()’ would be still a builtin function, while ‘require’ would become a language construct. Having that, ‘include()’ should allow to include code several times (i.e. in loop), while require should work as ‘require_once’.

Actually, we got 2 builtin function: include() and require(). Both of them are available only inside methods body. The proposition is to: * make 'require' available only on the global scope in order to include source files containing classes. * make 'include()' available only inside methods body, to include a part of code that will be executed during method call. Such code should be a valid AerScript code that can be executed inside method body (just like using 'eval()') Thus 'include()' would be still a builtin function, while 'require' would become a language construct. Having that, 'include()' should allow to include code several times (i.e. in loop), while require should work as 'require_once'.
belliash added the
bug
label 9 months ago
belliash added the
enhancement
label 9 months ago
belliash removed the
bug
label 9 months ago
belliash added the
idea
label 9 months ago
belliash commented 9 months ago
Owner

Additionally, ‘import()’ allows to load a shared AerScript module. Actually it is implemented as a built-in function returning TRUE on success, or FALSE otherwise. This gives the control to the software developer on potential fallback or throwing an exception it module is not available, when called from constructor for example. If we decide to rewrite it as language construct it would need to throw exception without ability to catch it from global scope.

Decision? I vote for having ‘include()’ and ‘import()’ builtin methods and ‘require’ language construct.

Additionally, 'import()' allows to load a shared AerScript module. Actually it is implemented as a built-in function returning TRUE on success, or FALSE otherwise. This gives the control to the software developer on potential fallback or throwing an exception it module is not available, when called from constructor for example. If we decide to rewrite it as language construct it would need to throw exception without ability to catch it from global scope. Decision? I vote for having 'include()' and 'import()' builtin methods and 'require' language construct.
belliash closed this issue 7 months ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.