Re: [boost] Command Line Config review results
At 09:12 AM 6/5/2003, Aleksey Gurtovoy wrote: Vladimir Prus wrote: There've been a fair amount of suggested changes, many of which are documented on Wiki [1], and since the author himself keeps track of the issues, I won't reiterate them here - except for stressing the need for a) extensively reworked and extended documentation, and Completely agree. b) resolving the 'wchar_t' support issue before the library makes into official Boost distribution. I'm actually not that happy about solving general issue alone... You don't have to. I am sure a lot of people on this list have dealt with the issue and would be happy to help you out. There may be a confusion here. Lots of people have experience with wchar_t and other non-char types in applications where the internal and external character set, type, size, and encoding are all the same. But I think command line arguments have to interoperate with the operating system. That means the internal and external character set, type, size, or encoding may be different. While some people have experience with character set conversions on specific operating systems, finding people who have solutions which work portably across multiple operating systems is much harder. --Beman ___ Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Command Line Config review results
At 10:48 AM 6/4/2003, Vladimir Prus wrote: Aleksey Gurtovoy wrote: b) resolving the 'wchar_t' support issue before the library makes into official Boost distribution. I'm actually not that happy about solving general issue alone... but let it be. I assume I've not asked to implement any specific approach, and can decide myself? I've just about finished an extensive analysis of the issues involved when wchar_t and other non-char types are used in filenames. Many of these issues, including the key interoperability requirements, will apply to command line arguments or any other communication where the character type, size, or encoding differs between internal use in a user program and external use by the operating system. It would be unwise and chaotic for the Boost filesystem and command line libraries to have different external to internal conversion behaviors. Also, those issues are fairly orthogonal to the other big picture aspects of a command line library design. All that argues for not trying to add wchar_t support to the command line library right away. --Beman ___ Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Command Line Config review results
Vladimir Prus wrote: There've been a fair amount of suggested changes, many of which are documented on Wiki [1], and since the author himself keeps track of the issues, I won't reiterate them here - except for stressing the need for a) extensively reworked and extended documentation, and Completely agree. b) resolving the 'wchar_t' support issue before the library makes into official Boost distribution. I'm actually not that happy about solving general issue alone... You don't have to. I am sure a lot of people on this list have dealt with the issue and would be happy to help you out. but let it be. I assume I've not asked to implement any specific approach, and can decide myself? I think the general conclusion was that one should be able to use both 'char' and 'wchar_t' versions of the library facilities in the same program. Aleksey ___ Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] Command Line Config review results
Aleksey Gurtovoy wrote: The Command Line Config library by Vladimir Prus has been accepted into Boost, pending the incorporation of suggestions brought up in the review. These are good news! I would like to thank all the reviewers. Being the library submitter is quite different from watching other reviews --- in particular, I was quite impressed with the number of good suggestions, and I think that the library will benefit greatly when they all are addressed. There've been a fair amount of suggested changes, many of which are documented on Wiki [1], and since the author himself keeps track of the issues, I won't reiterate them here - except for stressing the need for a) extensively reworked and extended documentation, and Completely agree. b) resolving the 'wchar_t' support issue before the library makes into official Boost distribution. I'm actually not that happy about solving general issue alone... but let it be. I assume I've not asked to implement any specific approach, and can decide myself? Also, as acting on the review comments should result in large number of interface and design changes, I suggest that after incorporating them in the library and before the public release the author posts a note to the list so that the interested parties have a chance to comment on the final version. That's my plan, actually. I think I'll look though all my notes and emails once again, and will either post a list of all planned changes to Wiki, or enter them into a publicly-available issue tracker, so that interested parties can add more opinions. As those issues are addressed, I'll inform the list. Thanks for all the comments, and to Aleksey for managing the review! - Volodya ___ Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
[boost] Command Line Config review results
The Command Line Config library by Vladimir Prus has been accepted into Boost, pending the incorporation of suggestions brought up in the review. Thanks to everyone for all their comments, and to Vladimir for being open and responsive to them! There've been a fair amount of suggested changes, many of which are documented on Wiki [1], and since the author himself keeps track of the issues, I won't reiterate them here - except for stressing the need for a) extensively reworked and extended documentation, and b) resolving the 'wchar_t' support issue before the library makes into official Boost distribution. Also, as acting on the review comments should result in large number of interface and design changes, I suggest that after incorporating them in the library and before the public release the author posts a note to the list so that the interested parties have a chance to comment on the final version. Once again, thanks to the author and all the reviewers. Aleksey Gurtovoy Command Line Config Review Manager [1] http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Program_Optio ns_Library_Pages ___ Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
