Sorry, that was my mistake. Version 2 has the space problem in 1.43, but not in 1.44. Version 3 is introduced in 1.44 but works in a different way and has the space problem. I don't know how well it (or lexical cast) handles L-strings. I've brought up the space issue on the development list, but I'm having a bit of trouble explaining it. Until a conclusion is reached, I'd suggest using strings in program options, and then constructing the filesystem path yourself.
Daniel
Food for the thought for the developers: In general, it would be confusing for lexical cast to do something different than a static cast, i.e. the constructor that takes a string as an argument. (In those cases where the ctor is indeed "converting" the string. When such a ctor form does something different, it makes sense that the lexical cast would be totally different.) Thanks, --John TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.