Karl Millar <[EMAIL PROTECTED]> writes:
> Peter Dimov wrote:
> [snip]
>>From: "David Abrahams" <[EMAIL PROTECTED]>
>>> Two areas that spring to mind are pointer comparisons outside a
>>> single array for unserializing internal object pointers, and the
>>> use of type_info::name() for type identification.
>>
>>Using type_info::name() means that when you recompile your program with
>>another compiler, or a newer version of the same compiler, it might no
>>longer be able to read its files.
I realize that. It still might make sense for some applications. For
example, imagine a build tool which stores a cache of its dependency
graph on disk to avoid re-scanning headers at each invocation. You
could write the compiler and version into the cache, and simply not
use it if the compiler/version don't match up.
Anyway, I'm by no means suggesting that this is appropriate for all or
even most applications. I'm just saying that it can be a useful and
labor-saving technique for some, and it would be nice if the library
allowed some way to exploit it.
--
David Abrahams
[EMAIL PROTECTED] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
