Hello all, I'm unable to execute the example from documentation:
bin/basex -b$v=example "declare variable $v external; $v"
IT gives this exception:
Stopped at ., 1/19: [XPST0003] Expecting '$', found 'e'.
Any clues? Regards, MArco.
Hi Marco,
I guess you run this as a shell command on a unix machine. $ is normally used for variables, so if you execute in from the shell directly, you might have to escape the dollar sign using , i.e. it would be
bin/basex -b$v=example "declare variable $v external; $v"
Cheers Dirk On 02/23/2015 04:44 PM, Marco Lettere wrote:
Hello all, I'm unable to execute the example from documentation:
bin/basex -b$v=example "declare variable $v external; $v"
IT gives this exception:
Stopped at ., 1/19: [XPST0003] Expecting '$', found 'e'.
Any clues? Regards, MArco.
Oh, thanks. Completely overlooked that. Will try. In the meantime is it possible, somehow, to parametrize calls to .bsx scripts when called through the RUN command from inside another .bsx? Thanks, Marco.
On 23/02/2015 17:56, Dirk Kirsten wrote:
Hi Marco,
I guess you run this as a shell command on a unix machine. $ is normally used for variables, so if you execute in from the shell directly, you might have to escape the dollar sign using , i.e. it would be
bin/basex -b\$v=example "declare variable \$v external; \$v"Cheers Dirk On 02/23/2015 04:44 PM, Marco Lettere wrote:
Hello all, I'm unable to execute the example from documentation:
bin/basex -b$v=example "declare variable $v external; $v"
IT gives this exception:
Stopped at ., 1/19: [XPST0003] Expecting '$', found 'e'.
Any clues? Regards, MArco.
Hi Marco,
In the meantime is it possible, somehow, to parametrize calls to .bsx scripts when called through the RUN command from inside another .bsx?
We are not quite sure where we should start and end with this, as it could also be nice to have conditions or try/catch clauses. On the other hand, we want to avoid creating a completely new scripting language..
But we already had some thoughts on how to best introduce parametrization in our command script syntax. Open questions are for example how parameters should be encoded to avoid ambiguities (example: $x could be an external command line parameter or part of an XQuery expression.. etc.).
We are glad to get more contributions on this; your suggestions are welcome!
Christian
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Dirk Kirsten -
Marco Lettere