One of the recurring problems in PipeScript, PowerShell, and programming is the grouping of related functionality.
Namespaces are the way that this is accomplished within many languages.
PowerShell doesn't really support that concept natively, though it has functionality that makes searching by wildcard (and thus namespace, easier).
PipeScript should support the concept of command namespaces.
The namespace of a command is anything before it's last dot or slash.
So, for example:
function Example.foo { } # declares foo in the example namespace
function .\Local\File\Path { } # declares Path in the local.file and local namespace
function github.com/repos { } # declares repos in github.com namespace
They could either by defined directly or via a syntax transpiler:
example function x {} # becomes function example x {}
.\Local\File function Path { } # declares .\Local\File\Path
github.com/ function repos { } # declares github.com/repos
One of the recurring problems in PipeScript, PowerShell, and programming is the grouping of related functionality.
Namespaces are the way that this is accomplished within many languages.
PowerShell doesn't really support that concept natively, though it has functionality that makes searching by wildcard (and thus namespace, easier).
PipeScript should support the concept of command namespaces.
The namespace of a command is anything before it's last dot or slash.
So, for example:
They could either by defined directly or via a syntax transpiler:
example function x {} # becomes function example x {} .\Local\File function Path { } # declares .\Local\File\Path github.com/ function repos { } # declares github.com/repos