Bug#199220: Bug#233052: acknowledged by developer (Bug#233052: fixed in ttcn3parser 20050122-1)

[W. Borgert]

Quoting Goswin von Brederlow <[EMAIL PROTECTED]>:
> [EMAIL PROTECTED] (Debian Bug Tracking System) writes:
> > Changes: 
> >  ttcn3parser (20050122-1) unstable; urgency=high
> >  .
> >* New upstream version by new upstream (me).
> >* No ANTLR anymore, using python-pyparsing instead.
> >* Follows the current TTCN-3 standard.
> >* Closes: #199220, #233052, #244274.
>
> Why?

Sorry for the shortspoken changelog, I will correct this in a
later version.  Here is the explanation:

As I changed the program from C++/ANTLR to Python/pyparsing,
there should be no problem with "invalid static_cast" anymore
(#233052) which is a C++ issue.  And there is no "unsatisfyable
Build-Depends" on ANTLR anymore (#244274) - it's not used.
And the new version does not crash (#199220).


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#233052: acknowledged by developer (Bug#233052: fixed in ttcn3parser 20050122-1)

[Goswin von Brederlow]

[EMAIL PROTECTED] (Debian Bug Tracking System) writes:

> Changes: 
>  ttcn3parser (20050122-1) unstable; urgency=high
>  .
>* New upstream version by new upstream (me).
>* No ANTLR anymore, using python-pyparsing instead.
>* Follows the current TTCN-3 standard.
>* Closes: #199220, #233052, #244274.

Why?

>* Lintian warnings fixed.

As discussed many times before don't just close bugs in the changelog
without comment.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]