Re: [boost] New Borland compiler _MSC_VER mess [was: Boost ships with C++ Builder X]

From: Daryle Walker (darylew_at_[hidden])
Date: 2003-11-28 21:06:56

On 11/27/03 10:58 AM, "Peter Dimov" <pdimov_at_[hidden]> wrote:

> Beman Dawes wrote:
>> 
>> Is this something we want to try to fix this release? There is
>> possibly suspect _MSC_VER use in the Boost headers listed below.
>> 
>> --Beman
>> 
>> boost\bind.hpp
>> boost\checked_delete.hpp
>> boost\current_function.hpp
>> boost\mem_fn.hpp
>> boost\ref.hpp
>> boost\throw_exception.hpp
>> boost\bind\arg.hpp
>> boost\bind\placeholders.hpp
>> boost\detail\atomic_count.hpp
>> boost\detail\atomic_count_win32.hpp
>> boost\detail\lightweight_mutex.hpp
>> boost\detail\lightweight_test.hpp
>> boost\detail\lwm_nop.hpp
>> boost\detail\lwm_pthreads.hpp
>> boost\detail\lwm_win32.hpp
>> boost\detail\lwm_win32_cs.hpp
>> boost\detail\lwm_win32_nt.hpp
>> boost\detail\quick_allocator.hpp
>> boost\detail\shared_count.hpp
> 
> These contain
> 
>   #if defined(_MSC_VER) && (_MSC_VER >= 1020)
>   #  pragma once
>   #endif
> 
> which is intentional. As a general rule, compilers that expose _MSC_VER do
> support "#pragma once".

Considering that there is an acceptable alternative that is completely
portable, I don't think the "#pragma once" is important enough to keep since
it forces the use of "_MSC_VER".

-- 
Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT hotmail DOT com