You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
Thank you for this great idea.
I was looking for a way to write, not only easier POSIX scripts, but if possible, to also have them be type safe. It will be enough to avoid typos in command names and make sure the variables contain the right kind of values.
Are the terms that call external programs checking the names in some way? Is there any option to do such thing? I understand that there should be a way to call arbitrary binaries, but having some of the most common ones be "built-in" will also be very nice.
Regards.
The text was updated successfully, but these errors were encountered:
That is super nice. I understand that you have to choose the smaller set of
features that is common to most grep versions (for example) and that is no
easy task to generalise.
If the executable, for some reason, is not available at runtime, will that
error be properly caught automatically? Or do I have to take care of that
in my program?
Hello.
Thank you for this great idea.
I was looking for a way to write, not only easier POSIX scripts, but if possible, to also have them be type safe. It will be enough to avoid typos in command names and make sure the variables contain the right kind of values.
Are the terms that call external programs checking the names in some way? Is there any option to do such thing? I understand that there should be a way to call arbitrary binaries, but having some of the most common ones be "built-in" will also be very nice.
Regards.
The text was updated successfully, but these errors were encountered: