- Boost - lists.boost.org

[private] To Jeff Garland
by Robert Kawulak 07 Feb '06

07 Feb '06

Hi, Sorry for posting this to the mailing list, but I've got no other way to contact. How can I contact you, Jeff? I was trying to send e-mails to the address given in the people page, but they don't seem to reach you. Best regards, Robert

1 0

[Release 1.34] Supported Compilers
by Thomas Witt 07 Feb '06

07 Feb '06

Hi, several recent posts touched the issue of deprecating compilers in the next release. Given the fact that we don't even seem to know what deprecating means I would like to propose the following: Compiler support should be phased out instead of dropped. I see three different stages here. Fully Supported --------------- Libraries should make an effort to support these compilers. Regressions in support version to version should be avoided. (Weasel wording intended). Full regression testing. Marked Deprecated ----------------- No effort is required to support these compilers in new functionality. Version to version regressions are accepted after the first version that marked these compilers as deprecated. Full regression testing (if resources are available). One key idea here is to give the user a good idea on the level of available functionality until a toolset reaches the "Unsupported" stage. Unsupported ----------- No regression testing is done. (Library authors might still support these toolsets for their libraries on a case by case basis.) AFAICS there seems to be strong support for moving gcc-2.95 and vc6 to "Marked Deprecated" and somebody needs to fight Alisdair over Borland (volunteers? any?). Comments Thomas -- Thomas Witt witt(a)acm.org

18 36

Filesystem I18n comments
by Martin 07 Feb '06

07 Feb '06

1. Why "directory_iterator->exists()" instead of "exists(directory_iterator)" 2. Any chance of having a non-throwing version of directory_iterator (similar to status). Since such a common error like not having access to a directory throws an exception, every directory_iterator construction needs a try/catch. The recursive_directory_iterator is kind of useless since it will stop as soon as you get an "access denied". (Maybe a portable can_be_iterated function can be added) 3. The documentation doesn't say how other_flag is supposed to work. If an implementation adds more flags, will other_flag be set for these? 4. A suggestion is to overload exists, is_directory etc for status flags and let the error condition be statusflags == 0. (or make status_flags a class with a bool conversion) In the code you could then write like if (status_flags s = status(path)) { if (!exists(s) || !is_directory(s)) cout << "bad directory"; } else cout << "error"; In the current implementation you need to remember if you should use == or & when checking the status flags. status_flags s = status(path); if (s == error_flag) // must test with == here cout << "error"; else if ((s & directory_flag) == 0) // must test with & here cout << "bad directory";

3 6

Re: [boost] [Review] Shmem
by Martin Bonner 07 Feb '06

07 Feb '06

----Original Message---- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Darren Cook Sent: 07 February 2006 08:06 To: boost(a)lists.boost.org Subject: Re: [boost] [Review] Shmem > 4. I didn't understand the first sentence in the limitations.html > page: > > "Shmem wants to be portable across multiple operating systems so that > it can not count with an operating systems that maps shared memory to > the same base address in all processes in the system" > > I think I'm stuck on "can not count with". I strongly suspect the original author meant "... so that it cannot count *on* an operating *system* that ...". I would rewrite the whole thing as: "Shmem is designed to be portable across multiple operating systems. As such it cannot rely on the operating system mapping shared memory to the same base address in each process." -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 203894

2 1

[typeof] is T registered?
by Andy Little 07 Feb '06

07 Feb '06

Hi to the typeof developers, I am wondering if it is possible to add some functionality so user can tell if a type is in the database of registered types during compilation. It may be there already of course. template <typename T> struct Func{ //one possible use case typedef typename boost::mpl::eval_if< boost::is_typeof_registered<T>, // true if T is registered typeof_operation<T>, // use BOOST_TYPEOF try_something_else<T> >::type type; }; Its not critical, but I thought it might be useful while libraries are adding the typeof functionality. Also might help me in the "[typeof] gcc and typeof in function return type" thread. regards Andy Little

3 4

Boost.Test: auto-linking breakage
by John Maddock 07 Feb '06

07 Feb '06

Boost.Test appears to be trying to autolink when it shouldn't - for example when including the boost/test/included/* headers again. See for example http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/output… John.

2 1

simple pyste test failure
by Neal Becker 07 Feb '06

07 Feb '06

I wanted to learn about pyste, so I tried the "hello world" example, but this is what I get: pyste.py --debug --module=hello world.pyste DEBUG: world.xml Traceback (most recent call last): File "/usr/bin/pyste.py", line 4, in ? pyste.main() File "/usr/lib/python2.4/site-packages/Pyste/pyste.py", line 418, in main status = Begin() File "/usr/lib/python2.4/site-packages/Pyste/pyste.py", line 257, in Begin return GenerateCode(parser, module, out, interfaces, multiple) File "/usr/lib/python2.4/site-packages/Pyste/pyste.py", line 376, in GenerateCode declarations, parsed_header = parser.Parse(header, interface, tail) File "/usr/lib/python2.4/site-packages/Pyste/CppParser.py", line 165, in Parse declarations = self.ParseWithGCCXML(header, tail) File "/usr/lib/python2.4/site-packages/Pyste/CppParser.py", line 128, in ParseWithGCCXML declarations = ParseDeclarations(xmlfile) File "/usr/lib/python2.4/site-packages/Pyste/GCCXMLParser.py", line 469, in ParseDeclarations parser.Parse(filename) File "/usr/lib/python2.4/site-packages/Pyste/GCCXMLParser.py", line 46, in Parse self.ParseElement(id, element) File "/usr/lib/python2.4/site-packages/Pyste/GCCXMLParser.py", line 70, in ParseElement func(id, element) File "/usr/lib/python2.4/site-packages/Pyste/GCCXMLParser.py", line 319, in ParseStruct self.ParseClass(id, element) File "/usr/lib/python2.4/site-packages/Pyste/GCCXMLParser.py", line 306, in ParseClass self.AddDecl(class_) File "/usr/lib/python2.4/site-packages/Pyste/GCCXMLParser.py", line 57, in AddDecl if decl.FullName() in self._names: File "/usr/lib/python2.4/site-packages/Pyste/declarations.py", line 48, in FullName return namespace + self.name TypeError: cannot concatenate 'str' and 'NoneType' objects ,----[ /home/nbecker/world.h ] | #include <string> | | struct World | { | void set(std::string msg) { this->msg = msg; } | std::string greet() { return msg; } | std::string msg; | }; `---- ,----[ /home/nbecker/world.pyste ] | Class("World", "world.h") | `----

1 0

serialization - archive with states eof, fail, bad instead of throwing exceptions?
by Oliver.Kowalke＠infineon.com 07 Feb '06

07 Feb '06

Hello, would it be possible to change the implementation of serialisation archives to support states eof, fail and bad as iostreams do. I would prefer to test for this states after serializing/deserializing objects from archives instead of get exceptions thrown. Regards, Oliver

1 0

iostreams::indirect_streambuf -> sync_impl returning integer?
by Oliver.Kowalke＠infineon.com 07 Feb '06

07 Feb '06

Hello, wouldn't it be better if indirect_streambuf::sync_impl returns a integer? In device::write I want to indicate that no character can be written to the external source via returning EOF (external device == socket -> peer has closed socket) instead throwing an exception. Regards, Oliver

1 0

Re: [boost] Regex Crash
by Wang Weiwei 07 Feb '06

07 Feb '06

>David Abrahams <dave(a)boost-consulting.com> writes: > >> Is a malformed regex supposed to crash the library? See enclosed .cpp file > >Sorry, I'm a fool; this was an exception from the library, but the >debugger showed me some line in the middle of the backtrace, so I >couldn't see it. > >-- >Dave Abrahams >Boost Consulting >www.boost-consulting.com >_______________________________________________ >Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost > use bad_expression for safeguard Wang Weiwei

1 0