[Cppunit-devel] help
Brought to you by:
blep
From: Chris R. <Chr...@sy...> - 2002-04-17 08:21:36
|
-----Original Message----- From: cpp...@li... [mailto:cpp...@li...] Sent: 16 April 2002 20:02 To: cpp...@li... Subject: Cppunit-devel digest, Vol 1 #172 - 6 msgs Send Cppunit-devel mailing list submissions to cpp...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/cppunit-devel or, via email, send a message with subject or body 'help' to cpp...@li... You can reach the person managing the list at cpp...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Cppunit-devel digest..." Today's Topics: 1. Re: Toward True Unicode Code... Help requested (Baptiste Lepilleur) 2. Re: Specifying coed page (was: Toward True Unicode Code... Help requested) (Baptiste Lepilleur) 3. Re: Signal handling in Linux (Baptiste Lepilleur) 4. Detecting --disable-test-plugin from configure.in (Baptiste Lepilleur) 5. Re: Toward True Unicode Code... Help requested (Duane Murphy) 6. Re: Toward True Unicode Code... Help requested (Baptiste Lepilleur) --__--__-- Message: 1 Reply-To: "Baptiste Lepilleur" <gai...@fr...> From: "Baptiste Lepilleur" <gai...@fr...> To: "CppUnit Developers" <cpp...@li...> Subject: Re: [Cppunit-devel] Toward True Unicode Code... Help requested Date: Tue, 16 Apr 2002 13:51:54 +0200 Organization: Gaia Creation ----- Original Message ----- From: "Duane Murphy" <dua...@ma...> To: "Baptiste Lepilleur" <gai...@fr...>; "CppUnit Developers" <cpp...@li...> Sent: Tuesday, April 16, 2002 1:37 AM Subject: Re: [Cppunit-devel] Toward True Unicode Code... Help requested > --- At Mon, 15 Apr 2002 23:32:29 +0200, Baptiste Lepilleur wrote: > > >----- Original Message ----- > >From: "Duane Murphy" <dua...@ma...> > >To: "CppUnit Developers" <cpp...@li...> > >Sent: Sunday, April 14, 2002 7:35 PM > >Subject: Re: [Cppunit-devel] Toward True Unicode Code... Help requested > > [...] > I hope I understand the question. If I output a string that includes a > '\n' in a stream, and some other process is parsing that stream, will > '\n' be unique? > > The answer is yes! I was equally stunned to here this. Once a shift > character is seen that identifies that following characters as unicode, > then none of the bytes that are part of that unicode "character" will be > less than 128! This is what makes UTF-8 work. All characters <128 are > always ASCII! Great, that means even ouputters relying on that are compatible with UTF8 (CompilerOutputter which as some line wrapping code). Baptiste. --__--__-- Message: 2 Reply-To: "Baptiste Lepilleur" <gai...@fr...> From: "Baptiste Lepilleur" <gai...@fr...> To: "CppUnit Developers" <cpp...@li...> Subject: Re: [Cppunit-devel] Specifying coed page (was: Toward True Unicode Code... Help requested) Date: Tue, 16 Apr 2002 13:57:46 +0200 Organization: Gaia Creation ----- Original Message ----- From: "Duane Murphy" <dua...@ma...> To: "Baptiste Lepilleur" <gai...@fr...>; "CppUnit Developers" <cpp...@li...> Sent: Tuesday, April 16, 2002 1:37 AM Subject: Re: [Cppunit-devel] Toward True Unicode Code... Help requested > --- At Mon, 15 Apr 2002 23:32:29 +0200, Baptiste Lepilleur wrote: > [...] > I'm not sure where you want to specify a code page and I'm not always > clear as to what a code page means in some contexts. I think (and this is > very old memory) that the encoding of an XML file can be UTF-8. Beyond > that, I dont know. The only stuff I know to specify code page is VC++ specific: // Set the locale setlocale( LC_ALL, "jpn" ); // Set the code associated to the current locale _setmbcp( _MB_CP_LOCALE ); When you do that, VC++ is supposed to use the specified locale when doing MBCS <=> UNICODE conversion. So, if you could specify a UTF8 code page, you would have a cheap way of doing UTF8/UNICODE conversion. (understand UNICODE as wchat_t ;-) ). Baptiste. --__--__-- Message: 3 Reply-To: "Baptiste Lepilleur" <gai...@fr...> From: "Baptiste Lepilleur" <gai...@fr...> To: <cpp...@li...> Subject: Re: [Cppunit-devel] Signal handling in Linux Date: Tue, 16 Apr 2002 14:34:18 +0200 Organization: Gaia Creation ----- Original Message ----- From: "Robert Wenner" <ro...@po...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Tuesday, April 16, 2002 7:58 AM Subject: Re: [Cppunit-devel] Signal handling in Linux > Hi! > > On Monday 15 April 2002 23:44, Baptiste Lepilleur wrote: > > So If I understood thing well, the only hope that remains would > > compiler specific. VC++ has such a thing, have you found anything > > like that on gcc ? (I guess not, but...) > > I think it would be compiler dependent, yes. > I do not know the exact behaviour in VC++, but I did not even found > something like a workaround on g++, as my C style stuff didn't work > as expected I quickly dropped that topic and tried to have test cases > that don't result in null pointer access -- not the bes solution, I > know... VC++ as a function called _set_se_translator() which allow you to set a 'translator' that is called to handle structured exception (the equivalent of signal if I understood correctly) and convert them into C++ exception. In any case, the stack frame is always unwinded correctly. Structured exception are the equivalent for VC++ to a throw int(exception_type) (in debug mode), which explains why catch(...) works for us even though we did not set any exception translator. > > > In the meantime, I think I'll add a VerboseTestProgressListener: > > startTest(): print test name > > failure(): print ':' and 'E' or 'F' > > endTest(): new line > Better to be names BriefTestProgressListener? Done. If you have others suggestions like that one, they are welcome. One of the step that will be taken before going beta is renaming 'not so intention revealing classes' (TestResult is a primary candidate but does not have its final form yet). Thanks, Baptiste. --__--__-- Message: 4 Reply-To: "Baptiste Lepilleur" <gai...@fr...> From: "Baptiste Lepilleur" <gai...@fr...> To: <cpp...@li...> Date: Tue, 16 Apr 2002 15:52:46 +0200 Organization: Gaia Creation Subject: [Cppunit-devel] Detecting --disable-test-plugin from configure.in I was reading some of the autobook. Will adding the following code after the USE_TYPE_INFO to configure.in, will define the symbol CPPUNIT_NO_TESTPLUGIN if --disable-test-plugin is used on the command line ? AC_ARG_ENABLE(test-plugin, [ --disable-test-plugin disable support for test plug-ins], [ if test -n "$enable_test_plugin"; then enable_test_plugin=${enable_test_plugin_default-yes} fi if test "$enable_test_plugin" = no; then AC_DEFINE(NO_TESTPLUGIN) fi ]) Baptiste. --__--__-- Message: 5 From: Duane Murphy <dua...@ma...> To: Baptiste Lepilleur <gai...@fr...>, CppUnit Developers <cpp...@li...> Subject: Re: [Cppunit-devel] Toward True Unicode Code... Help requested Date: Tue, 16 Apr 2002 08:28:46 -0700 --- At Tue, 16 Apr 2002 13:51:54 +0200, Baptiste Lepilleur wrote: >----- Original Message ----- >From: "Duane Murphy" <dua...@ma...> >To: "Baptiste Lepilleur" <gai...@fr...>; "CppUnit Developers" ><cpp...@li...> >Sent: Tuesday, April 16, 2002 1:37 AM >Subject: Re: [Cppunit-devel] Toward True Unicode Code... Help requested > > >> --- At Mon, 15 Apr 2002 23:32:29 +0200, Baptiste Lepilleur wrote: >> >> >----- Original Message ----- >> >From: "Duane Murphy" <dua...@ma...> >> >To: "CppUnit Developers" <cpp...@li...> >> >Sent: Sunday, April 14, 2002 7:35 PM >> >Subject: Re: [Cppunit-devel] Toward True Unicode Code... Help requested >> > >[...] >> I hope I understand the question. If I output a string that includes a >> '\n' in a stream, and some other process is parsing that stream, will >> '\n' be unique? >> >> The answer is yes! I was equally stunned to here this. Once a shift >> character is seen that identifies that following characters as unicode, >> then none of the bytes that are part of that unicode "character" will be >> less than 128! This is what makes UTF-8 work. All characters <128 are >> always ASCII! > >Great, that means even ouputters relying on that are compatible with UTF8 >(CompilerOutputter which as some line wrapping code). I want to make sure that this question is properly understood. If you are just searching for '\n' in a stream or string then that will work fine. If you are looking to insert '\n' (or any other characters) at some position then things get complicated. ...Duane -- "If tyranny and oppression come to this land, it will be in the guise of fighting a foreign enemy." - James Madison --__--__-- Message: 6 Reply-To: "Baptiste Lepilleur" <gai...@fr...> From: "Baptiste Lepilleur" <gai...@fr...> To: "CppUnit Developers" <cpp...@li...> Subject: Re: [Cppunit-devel] Toward True Unicode Code... Help requested Date: Tue, 16 Apr 2002 20:28:56 +0200 Organization: Gaia Creation ----- Original Message ----- From: "Duane Murphy" <dua...@ma...> To: "Baptiste Lepilleur" <gai...@fr...>; "CppUnit Developers" <cpp...@li...> Sent: Tuesday, April 16, 2002 5:28 PM Subject: Re: [Cppunit-devel] Toward True Unicode Code... Help requested > --- At Tue, 16 Apr 2002 13:51:54 +0200, Baptiste Lepilleur wrote: > >----- Original Message ----- > >From: "Duane Murphy" <dua...@ma...> > >To: "Baptiste Lepilleur" <gai...@fr...>; "CppUnit Developers" > ><cpp...@li...> > >Sent: Tuesday, April 16, 2002 1:37 AM > >Subject: Re: [Cppunit-devel] Toward True Unicode Code... Help requested > > > > > >> --- At Mon, 15 Apr 2002 23:32:29 +0200, Baptiste Lepilleur wrote: > >> > >> >----- Original Message ----- > >> >From: "Duane Murphy" <dua...@ma...> > >> >To: "CppUnit Developers" <cpp...@li...> > >> >Sent: Sunday, April 14, 2002 7:35 PM > >> >Subject: Re: [Cppunit-devel] Toward True Unicode Code... Help requested > >> > > >[...] > >> I hope I understand the question. If I output a string that includes a > >> '\n' in a stream, and some other process is parsing that stream, will > >> '\n' be unique? > >> > >> The answer is yes! I was equally stunned to here this. Once a shift > >> character is seen that identifies that following characters as unicode, > >> then none of the bytes that are part of that unicode "character" will be > >> less than 128! This is what makes UTF-8 work. All characters <128 are > >> always ASCII! > > > >Great, that means even ouputters relying on that are compatible with UTF8 > >(CompilerOutputter which as some line wrapping code). > > I want to make sure that this question is properly understood. If you are > just searching for '\n' in a stream or string then that will work fine. > If you are looking to insert '\n' (or any other characters) at some > position then things get complicated. You understood the question well. It's me who did not have all my head when I answered. Indeed I insert '\n', which make it not UTF8 compatible. This is an issue that will need to be addressed in the future. Thanks, Baptiste. > > ...Duane > > -- > "If tyranny and oppression come to this land, it will be in the > guise of fighting a foreign enemy." - James Madison > > > --__--__-- _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel End of Cppunit-devel Digest |