Rene Engelhard wrote:
> Am Mittwoch, 22. November 2006 14:55 schrieb Stephan
Bergmann:
>> Is this change really clean? While it is important
that standard
>
> It is, afaik.
>
>> headers are
>>
>> #include <map>
>>
>> etc. the situation is different for non-standard
headers like STLport's
>> hash_map. (We repeatedly had the discussion
whether headers delivered
>> by one part of OOo and used within another part of
OOo should be
>> included <...> or "...". We do not
need to repeat that discussion here,
>> as we obviously come to no agreement, and it might
be considered a
>> matter of style which to choose.)
>
> There's three possibilities:
>
> a) use OOos internal stlport. In this case the -I to
the internal one gets
> added and iirc that takes precedence
>
> b) external stlport. You specify the stlport home and
the include also gets
> set
>
> c) build with gccs stl (never tried that but it's
supported by configure) in
> which case this shouldn't be a problem either.
>
> Regards,
>
> Rene
I did not mean clean as "happens to work with the
current
constellations," but rather clean as "as
conforming as possible to any
relevant standards, to avoid potential future
problems."
-Stephan
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe porting.openoffice.org
For additional commands, e-mail: dev-helpporting.openoffice.org
|