nugend/qutil

Q Utilities

qutil's Issues

Dashes in command line parameters aren't parsing correctly

example fail-fast in qspec

Bug with libraries containing dashes in the name

They can't be read properly. Fix it.

Binary Option Flag is not working with multiple flag values

In this example:

.utl.require "ln"
.utl.addOpt["foo,foobar";1b;`foo];
.utl.parseArgs[];
show foo;
exit 0

foobar cannot be used to set the flag

Always resolve loading files to absolute path.

Files can be reloaded if the first time a file is referred to, a relative path is used, but later a loaded file resolves a name through the global package namespace. On the second occurrence, an absolute path will be used to determine the file identity.

This could also be a problem if two sets of files are somehow loaded relatively and the same name is present in each set.

Access to environment variables in config parser

Add the option to search for environment variables during name substitution:

java = %(JAVA_HOME)/bin/java

init.q optional in one-file package

In a lean package with just a single file, there is no need for the boilerplate overhead of init.q. At least, init.q should be optional, not mandatory.

$ ls $QPATH/my-1.0.0
my.q
$ cat $QPATH/my-1.0.0/my.q
\d .my

This conditional statement:

qutil/lib/bootstrap.q

Line 17 in 2bce9de

file: $[not 11h ~ type key pkgInfo[`file];pkgInfo[`file];` sv pkgInfo[`file],`init.q];

will resolve to false even for single-file directory:

q) key pkgInfo`file 
,my.q
q) not 11h ~ type key pkgInfo`file
0b

Was it intended?

I propose changing the line to:

file:` sv f,$[f~k:key f:pkgInfo`file;();1=count k;first k;`init.q];

That will nicely cover all scenarios:

q).utl.require"my/my.q"    / file loading scenario
q).utl.require"my"         / dir loading scenario; supports single-file dir with or without init.q

Change API from .utl.addOpt to .utl.addFlag

In the history of the command line parser's development, addOpt was created before addOptDef and intended to support both command line flags that would take an argument as well as command line flags that toggled an option on or off.

After using the library for a long time, the addOptDef is used far more often and addOpt is actually confused by its capability of parsing a parameter. Consequently, I want to create addFlag as a limited subset of addOpt which only supports boolean flags and eventually remove addOpt as it exists altogether.

Non-boolean parameter flags should indicate an error if there is no argument present

In this example

.utl.require "ln"
.utl.addOptDef["foo";"S";`bar;`foo];
.utl.parseArgs[];
show foo;
exit 0

If the program is called with "--foo" and no value is passed to the option, a command line error should occur.