Re: Some VMS errors in DBI trunk

  On 11/09/2010 16:20, Craig A. Berry wrote:
> In article<[email protected]>,
>   [email protected] ("Martin J. Evans") wrote:
>
>> On 09/09/10 15:18, Martin J. Evans wrote:
>>> v20 $ perl -I[.blib.lib] -I[.blib.arch] [.t]19fhtrace.t
>>> 1..27
>>> ok 1 - use DBI;
>>> Can't set DBI::db=HASH(0x38c68c)->{PrintWarn}: unrecognised attribute or
>>> invalid
>>>   value at /perl_root/lib/site_perl/DBD/ExampleP.pm line 230.
>>> # Looks like you planned 27 tests but ran 1.
>>> # Looks like your test exited with 1024 just after 1.
>>> %SYSTEM-F-ABORT, abort
>> This one was down to the fact that those -Is on the command line are not
>> working.
> Depending on your VMS version you can
>
> $ define DECC$ARGV_PARSE_STYLE ENABLE
>
> to preserve the case of command-line arguments, or, on any VMS version,
> use double quotes like so:
>
> $ perl -"I[.blib.lib]" -"I[.blib.arch]" [.t]19fhtrace.t
Thanks Craig.

I did in fact know those solutions but it has been many years since I 
actively worked on VMS and my memory has dulled. I had executed "set 
process/parse=extended" thinking that was what sorted it. Funnily enough 
I remembered most of the Gold/PF1 key combinations for editing in 
edt/lse but only by not trying to remember them and just doing what came 
naturally to me but then I had a battle trying to get a vt220-like 
terminal in Ubuntu Linux.  By the time I'd got going again a colleague 
reminded me I'd installed both vim and emacs!

Thanks again for the reminder and for letting me cajole you into taking 
a look.

Martin