Wireshark-dev: Re: [Wireshark-dev] ASN.1 generating unused code warnings (was:Compile warnings
From: "Kukosa, Tomas" <tomas.kukosa@xxxxxxxxxxx>
Date: Wed, 25 Jun 2008 08:38:31 +0200
It can be ignored e.g. with following .cnf direcive

#.OMIT_ASSIGNMENT
OR-Set
AND-Set
#.END

BTW if the OR-Set is not used inside FTAM it does not mean it is
unnecessary from ASN.1 point of view. It can be imported into another
ASN.1 specification. 

Tomas
 

> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx 
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Joerg Mayer
> Sent: Wednesday, June 25, 2008 7:46 AM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] ASN.1 generating unused code 
> warnings (was:Compile warnings using CFLAGS 
> '-Wshadow-Wpointer-arith-Wcast-qual -W -Wall' )
> 
> On Tue, Jun 24, 2008 at 10:52:04PM +0200, Anders Broman wrote:
> > Not sure I have to check later, but it may well be in the 
> original ASN.1
> > file. I seem to remember looking at some of those warnings 
> before and being
> > undecided whether we should comment out unused ASN.1 code 
> in *our* ASN.1
> > file or keep the original ones as far as possible.
> 
> Maybe adding an option to ignore parts of the asn spec 
> instead of commenting
> things out in the asn file could be used. Leaving the asn 
> file untouched is
> nice from a maintainance point of view, commenting out 
> unnecessary/unwanted
> stuff is nice from an implementation point of view.
> 
>  ciao
>   Joerg
> -- 
> Joerg Mayer                                           
> <jmayer@xxxxxxxxx>
> We are stuck with technology when what we really want is just 
> stuff that
> works. Some say that should read Microsoft instead of technology.
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> https://wireshark.org/mailman/listinfo/wireshark-dev
>