Re: Nice explaination what happens with idls.

[Ken Foskey <waratah@zip.com.au>]

For a lead in on this.  I have filed a bug on GCC with the -Wall option 
(4558).  It flags the true MININT value as a warning.  Reading the GCC 
manual it actually describes this as a non bug,  an ISO requirement to 
analyse the number first.  I think it probably should not with the 
explicit caste before hand.

I will have to patch the Open Office program that builds the *hdl file 
to use the same logic as limits.h   (-(MAX_INT)-1).   All this to 
compile -Wall without many messages.

On this, there is a warning I think I understand but I would like 
someone to tell me why this is is a warning and what the possible 
consequences are.

/data/office/solver/638/unxlngi3.pro/inc/cppuhelper/propshlp.hxx:584: 
warning: `class cppu::OPropertySetHelper' has virtual functions but 
non-virtual destructor

Lifes little challenges...
KenF

Bernhard R. Link wrote:

> ----- Forwarded message from Joerg Barfurth <jub@sun.com> -----
>
> From: Joerg Barfurth <jub@sun.com>
> Reply-To: dev@tools.openoffice.org
> Date: Sat, 13 Oct 2001 23:40:26 +0200
> To: <dev@tools.openoffice.org>
> Subject: Re: [tools-dev] Potential GCC -Wall problem.
> Delivered-To: mailing list dev@tools.openoffice.org
>
> Hi Ken,
>
> am 13.10.2001 13:15 Uhr schrieb Ken Foskey (foskey@optushome.com.au):
>
> > This brings me back to the original question.   How does
> > unxlngi3.pro/inc/com/sun/star/awt/VclWindowPeerAttribute.hdl get created?
> >
> > KenF
>
> Usually all *.hdl files are C++-headers generated from a UNO registry by
> cppumaker. The complete process is as follows:
>
> Somewhere there is a IDL file (a likely candidate for <project> might be
> 'offapi'):
>   <project>/com/sun/star/awt/VclWindowPeerAttribute.idl
>
> > From that idlc produces a VclWindowPeerAttribute.urd, which gets merged by
> regmerge into a <something>.rdb, from which finally a applicat.rdb gets
> created and delivered in 'drafts'.
>
> That 'registry database' file contains all the UNO Types known to the
> OpenOffice.org application.
>
> Later cppumaker is invoked to generate the C++ headers for type
> com.sun.star.awt.VclWindowPeerAttribute from this rdb. For higher-level
> modules this usually is taken care of in module 'offuh' ('uh' <=> 'UNO
> Headers').
> This step generates headers VclWindowPeerAttribute.hdl and
> VclWindowPeerAttribute.hpp.
>
> Note: The *.hdl contains the actual type or constant definition. The *.hpp
> includes the *.hdl and contains inline implementations of member functions.
> Usually user code whould include the *.hpp.
>
> HTH, Jörg