Re: More unicode problems

2006-08-21 Thread Abdelrazak Younes
Hossein Noorikhah wrote: Hi. Has anyone applied the patch on SVN? I'm still having this problem with the latest SVN version(revision 14809) of the Lars Gullik Bjønnes's unicode branch, using Debian Sarge with gcc version 3.3.5. Hello Hossein, The unicode branch has been merged in trunk. I thin

Re: More unicode problems

2006-08-21 Thread Hossein Noorikhah
Hi. Has anyone applied the patch on SVN? I'm still having this problem with the latest SVN version(revision 14809) of the Lars Gullik Bjønnes's unicode branch, using Debian Sarge with gcc version 3.3.5. Hossein

Re: More unicode problems

2006-08-15 Thread Georg Baum
Lars Gullik Bjønnes wrote: > Georg Baum <[EMAIL PROTECTED]> > writes: > > | Could we not simply put the template solution in? Even if you'd like the > | other one better, this is code for an older compiler that will go away > | some day. I just don't think that we should drop support for gcc 3.3

Re: More unicode problems

2006-08-15 Thread Lars Gullik Bjønnes
Georg Baum <[EMAIL PROTECTED]> writes: | Could we not simply put the template solution in? Even if you'd like the | other one better, this is code for an older compiler that will go away some | day. I just don't think that we should drop support for gcc 3.3 now. Yes. Put that in for now. I'll hav

Re: More unicode problems

2006-08-15 Thread Georg Baum
Lars Gullik Bjønnes wrote: > You are saying that we cannot have a > > template<> char_traits in the header file? At least it does not work for some of the functions. I tried that, and the result was multiple definitions of at least char_traits::eof()eof() at the linking stage. There were more, b

Re: More unicode problems

2006-08-15 Thread Lars Gullik Bjønnes
Georg Baum <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes wrote: | | > Georg Baum <[EMAIL PROTECTED]> | > writes: | > | > | Am Montag, 14. August 2006 20:11 schrieb Lars Gullik Bjønnes: | > | > Ahh... that is what you have done. | > | > But we should not add the templates ourself I think. O

Re: More unicode problems

2006-08-15 Thread Georg Baum
Lars Gullik Bjønnes wrote: > Georg Baum <[EMAIL PROTECTED]> > writes: > > | Am Montag, 14. August 2006 20:11 schrieb Lars Gullik Bjønnes: > | > Ahh... that is what you have done. > | > But we should not add the templates ourself I think. Only the explit > | > specialization of the functions. > |

Re: More unicode problems

2006-08-14 Thread Lars Gullik Bjønnes
Georg Baum <[EMAIL PROTECTED]> writes: | Am Montag, 14. August 2006 20:11 schrieb Lars Gullik Bjønnes: | > Ahh... that is what you have done. | > But we should not add the templates ourself I think. Only the explit | > specialization of the functions. | > | > And we should make it be complete. (g

Re: More unicode problems

2006-08-14 Thread Georg Baum
Am Montag, 14. August 2006 20:11 schrieb Lars Gullik Bjønnes: > Ahh... that is what you have done. > But we should not add the templates ourself I think. Only the explit > specialization of the functions. > > And we should make it be complete. (gut feeling...) OK, I can do both, but you did not a

Re: More unicode problems

2006-08-14 Thread Lars Gullik Bjønnes
Georg Baum <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes wrote: | | > Georg Baum <[EMAIL PROTECTED]> | > writes: | > | > | Lars, | > | | > | I get several undefined references like this one with current trunk (gcc | > | 3.3.5, 32 bit): | > | > Your gcc is too old, and to fix it we must pr

Re: More unicode problems

2006-08-14 Thread Georg Baum
Lars Gullik Bjønnes wrote: > Georg Baum <[EMAIL PROTECTED]> > writes: > > | Lars, > | > | I get several undefined references like this one with current trunk (gcc > | 3.3.5, 32 bit): > > Your gcc is too old, and to fix it we must provide the specialization > fo char_traits ourselves. Gcc4 has b

Re: More unicode problems

2006-08-14 Thread Lars Gullik Bjønnes
Georg Baum <[EMAIL PROTECTED]> writes: | Lars, | | I get several undefined references like this one with current trunk (gcc | 3.3.5, 32 bit): Your gcc is too old, and to fix it we must provide the specialization fo char_traits ourselves. Gcc4 has better QoI and does the work for us. | frontends

More unicode problems

2006-08-14 Thread Georg Baum
Lars, I get several undefined references like this one with current trunk (gcc 3.3.5, 32 bit): frontends/qt3/.libs/libqt3.a(qfont_metrics.o (.gnu.linkonce.t._ZNSbIjSt11char_traitsIjESaIjEE13_S_copy_charsEPjS3_S3_+0x1c): In function `std::basic_string, std::allocator >::_S_copy_chars(unsigned*, un