This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Another idea for 6015



> My idea is the following: /after/ snprintf has done its work, due to MT, 
> it could be possible that __out has the wrong decimal point, that is 
> /not "."/, as we expect. We expect the "C" decimal point.
> Therefore, conditionalized to ("MT" && !glibc2.3) we look for the actual 
> decimal point and we fix it to ".". This is thread-safe, completely.

I thought that snprintf would fail due to the expected separator in the
current locale differing from the "C" separator in __out, so that __v
wouldn't even be valid. 

At this point, I'm not quite sure I understand you. The testsuites test 
for this situation, so if you feel like you have a solution that would 
work, I suggest you experiment, hack the code, and see if the testsuites 
pass. If they do, let me know about what you've got.....

I remain convinced that the best solution is your first one.

Sorry,
benjamin


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]