Hi Ronnie,
your correction is right. I forgot it when I moved value_string emitting
from eth_type_fn() to eth_type_vals().
You can remove it including one line before (i.e. vals = []).
The next error concerning ber_structure containing an undefined variable I
will investigate on Monday.
Tomas
> Hi Tomas
>
> I encountered a problem with the asn2eth compiler emitting the
> value_string
> for an
> enumerated integer twice.
>
> I tracked it down in the compiler to these two places and commenting out
> the
> second instance
> stopped it from emitting it twice.
>
> Please see attached diff.
> Is this the right solution to the problem? I am not a python person and
> have
> not grasped the compiler
> and how it works yet.
>
>
> I also renamed a BER constant from BER_UNI_TAG_UCTTime to
> BER_UNI_TAG_UTCTime as that is what
> X.680 calls it.
>
>
> ----- Original Message -----
> From: "Ronnie Sahlberg"
> Sent: Friday, June 04, 2004 11:16 PM
> Subject: Re: [Ethereal-dev] H235 & ASN1 compiler
>
>
>> Hi,
>>
>> I have checked in your changes in the other mail.
>>
>> I am still trying to battle with X509 and have made some progress.
>> Thanks
>> for the feedback below.
>>
>> The compiler can as i understand it not handle parameterized types so
>> i
>> massaged the asn1 file to
>> not use parameterized types at all.
>> Now it then generates a pretty complete dissector (with dependencies on
>> other modules however)
>> but it will not compile.
>>
>> The compiler has generated a ber_structure containing an undefined
> variable
>> imp
>> For example, see the structure : static ber_sequence
>> T_signedCertificate_sequence[] = {
>>
>> The compiler also complains about the unknown define
>> BER_UNI_TAG_UTCTime
>> in the generated file.
>>
>>
>> Please assist.
>>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
