support in that version of libstdc++ was an
all-or-nothing thing, and I don't think wer should change that.
Fine. I'll leave that alone until we have all the functions it wants.
On second thought, wouldn't leaving this bit out mean that C++
applications won't be able to use wscanf
thought, wouldn't leaving this bit out mean that C++
applications won't be able to use wscanf on gcc3 architectures?
Not really. They just won't be in the std:: namesapce. But you can
still access them in the global namespace.
The thing I'm worried about is code that makes assumptioms
, and I don't think wer should change that.
Fine. I'll leave that alone until we have all the functions it wants.
On second thought, wouldn't leaving this bit out mean that C++
applications won't be able to use wscanf on gcc3 architectures?
Not really. They just won't be in the std
On Tue, Sep 20, 2011 at 06:09:34PM +0200, Stefan Sperling wrote:
On Tue, Sep 20, 2011 at 12:01:18PM +0200, Stefan Sperling wrote:
wscanf based on our scanf implementation. The delta from narrow
to wide character support was obtained from FreeBSD and modified
to fit our code.
Does
wscanf based on our scanf implementation. The delta from narrow
to wide character support was obtained from FreeBSD and modified
to fit our code.
Does not include a libc bump yet!
Here are corresponding libstdc++ changes, also without bumps.
The gcc3 version will have to be revisited
_GLIBCPP_USE_WCHAR_T unless it finds all wchar functions it wants).
Not sure if the c_compatibility change is really needed.
We didn't update it for wprintf (by accident?)
Need to look into this.
Can someone run this (together with the libc wscanf diff) through a build
on gcc2 and gcc3
On Wed, Sep 21, 2011 at 06:13:31PM +0200, Mark Kettenis wrote:
wide character support in that version of libstdc++ was an
all-or-nothing thing, and I don't think wer should change that.
Fine. I'll leave that alone until we have all the functions it wants.
Get working on wcsfstime() ;)
AFAIK
Mark Kettenis mark.kette...@xs4all.nl wrote:
Can someone run this (together with the libc wscanf diff) through a build
on gcc2 and gcc3 architectures?
I don't think you should commit the following gcc3:
-snip-
wide character support in that version of libstdc++ was an
all-or-nothing
have all the functions it wants.
On second thought, wouldn't leaving this bit out mean that C++
applications won't be able to use wscanf on gcc3 architectures?
AFAICT libstdc++ doesn't use these functions itself.
It just declares them in the std:: namespace so C++ apps can use them.
wscanf based on our scanf implementation. The delta from narrow
to wide character support was obtained from FreeBSD and modified
to fit our code.
Does not include a libc bump yet!
Please also review the diff between vfscanf.c and vfwscanf.c after
applying this. Thanks.
Index: include/wchar.h
On Tue, Sep 20, 2011 at 12:01:18PM +0200, Stefan Sperling wrote:
wscanf based on our scanf implementation. The delta from narrow
to wide character support was obtained from FreeBSD and modified
to fit our code.
Does not include a libc bump yet!
Here are corresponding libstdc++ changes, also
Hello all.
I saw this patch adding wscanf(3) implementation:
http://marc.info/?l=openbsd-techm=130005550717332w=2
What's the current plans for wprintf(3)/wscanf(3) support are? It could
be used in Virtuoso port; otherwise, nasty hacks will have to come in.
I'll add them until wscanf(3) support
On Fri, Sep 09, 2011 at 04:00:10PM +0400, Vadim Zhukov wrote:
Hello all.
I saw this patch adding wscanf(3) implementation:
http://marc.info/?l=openbsd-techm=130005550717332w=2
What's the current plans for wprintf(3)/wscanf(3) support are? It could
be used in Virtuoso port; otherwise
13 matches
Mail list logo
