In Shell 2.0, if I try to pass a '|' in a double-quoted string argument to
a .efi utility, the shell does not honor the double quote marks, truncates
the argument at the '|' and includes the opening '"' as part of the argument:
2.0 FS0:> utility "/t=aaabbb" "/r=a+|b"
ERROR: utility: Invalid argument: '"/r=a+'
If I "escape" the '|' by prefacing it with a '^', the shell no longer
truncates the argument, but neither does it strip out the '^' before passing
the argument to the .efi utility:
2.0 FS0:> utility "/t=aaabbb" "/r=a+^|b"
ERROR: utility: Invalid argument: '/r=a+^|b'
Both of these behaviors seem in error to me... Comments?
Regards,
Jim
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
