[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20010629: alloc.h

Unidata Support wrote:
> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >cc: Paul Hamer <address@hidden>
> >From: Paul Hamer <address@hidden>
> >Subject: alloc.h
> >Organization: UCAR/Unidata
> >Keywords: 200106292304.f5TN4M109472
> 
> Hello there,
> 
> A quick question on alloc.h, why is it copied to
> ~ldm/include? The reason I ask is that GCC also
> has a alloc.h for the STL and the ldm alloc.h
> causes problems for some template handling with
> the standard library. It seems that the makefile
> scheme uses -I../misc to find the ldm version of
> the file and it's not included by other header
> file so I'm not sure why it's copied.
> 
> Thanks,
> 
> Paul.
> 
> --
> Paul Hamer
> phone: 303.497.6342
> 
> ------- End of Forwarded Message

Hi Paul,

Hmmm, I see what you mean.  

Offhand, I don't see why it's copied to the 'include' dir, except that
it's the traditional thing to do.  Maybe the real question is why the
LDM is set up to include from 'misc' and not 'include'.  It may be for
hysteric..., er, historical reasons.  I will ask my clever and talented
coworkers and let you know if I find out anything.  

Are you building things that use pieces of the LDM?  How is it that
you're picking up the LDM's alloc.h in your builds?

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************