Featuring LIBRARY PATH AND NAME
What syntax would you like for the LIBRARY PATH AND NAME part?
What should be the sub-directory separator? '/' vs '.' vs "'s'" vs other keywords
Is '..' (relative parent directory) allowed?
Are there relative/absolute "LIBRARY" and default <LIBRARY> path look-up syntax, like in C language?
Are there default library search path mechanisms, like ROCKSTAR_PATH=.:/etc/rockstar_std_lib?
Personally I like the 's because it looks English, however the grammar should not be ambiguous with the current is assignment contraction. Also having some more aliases would avoid having 's repeatedly in longer paths.
I don't really like, for security reasons, allowing the code to include anything from anywhere. Thus I would ban absolute path /blabla and random locations ../other. Instead I would limit the search, like in Python, to the relative children directories child/grandchild/library and the default locations listed in a ROCKSTAR_PATH environment variable. The implementation would search in order: in the directory of the currently executed (or imported) file, then in ROCKSTAR_PATH, then in an implementation dependent location which would contain the standard library followed by other implementation specific libraries.
This discussion follows the pull request 314
Featuring LIBRARY PATH AND NAMEWhat syntax would you like for theLIBRARY PATH AND NAMEpart?"LIBRARY"and default<LIBRARY>path look-up syntax, like in C language?Personally I like the
'sbecause it looks English, however the grammar should not be ambiguous with the currentisassignment contraction. Also having some more aliases would avoid having'srepeatedly in longer paths.I don't really like, for security reasons, allowing the code to include anything from anywhere. Thus I would ban absolute path
/blablaand random locations../other. Instead I would limit the search, like in Python, to the relative children directorieschild/grandchild/libraryand the default locations listed in a ROCKSTAR_PATH environment variable. The implementation would search in order: in the directory of the currently executed (or imported) file, then in ROCKSTAR_PATH, then in an implementation dependent location which would contain the standard library followed by other implementation specific libraries.What do you think?