Re: Found problem mentioned in email 3/27: path interpretted/eval'd as numeric expression

2013-04-18 Thread Linda Walsh
Chris Down wrote: > On 2013-04-17 17:30, Linda Walsh wrote: >> BTW, is it planned to implement exporting ARRAY and HASHES? >> >> Sure would simplify some programs... ;-) > > As if exporting functions wasn't hacky enough... But then the function would have produced consistent results

Re: Found problem mentioned in email 3/27: path interpretted/eval'd as numeric expression

2013-04-17 Thread Chris Down
On 2013-04-17 17:30, Linda Walsh wrote: > BTW, is it planned to implement exporting ARRAY and HASHES? > > Sure would simplify some programs... ;-) As if exporting functions wasn't hacky enough... pgpgq8C_hz5oQ.pgp Description: PGP signature

Found problem mentioned in email 3/27: path interpretted/eval'd as numeric expression

2013-04-17 Thread Linda Walsh
I'm leaning toward the side of this not being a bug, BUT is it really this way?? Really seems a buried "gotcha" and maybe behavior should be reconsidered if this is desirable. I have a function "include", that looks along my PATH for the file. One might ask why shopt -s sourcepath doesn't work: