This bug does not exist in any recent version of unifdef. It was fixed
over five years ago.
commit 0c5e37ded46c073f2a03878726d703df026b88a3
Author: Tony Finch d...@dotat.at
Date: 2005-03-08 12:07:27 +
Update the copyright notice to the FreeBSD standard.
Do not recognize comment
severity 603860 normal
tag 603860 + lenny
thanks
Ken Raeburn wrote:
char foo[] = rm -rf /*;
Thank you for your bug report and the nice test case that you
included. Having a small test case such as that was wonderful. I
have confirmed the problem you reported does exist in Debian Stable.
Bob Proulx wrote:
The version in Squeeze does not suffer from
this problem. As Tony noted it has already been fixed upstream. It
has already propagated into Debian Unstable Sid and is only waiting
for the release of Squeeze as Stable.
That's good to know; thank you. I'll pass that on
Ken Raeburn wrote:
That's good to know; thank you. I'll pass that on to our admins and
see if they want to pull down the newer package.
I just verified that the dependencies for the Squeeze version of the
package are still valid for Lenny. The newer version in Squeeze may
be installed on
Package: unifdef
Version: 1.0+20030701-1
Severity: important
Running unifdef -UBARF over the file:
char foo[] = rm -rf /*;
causes a warning that the file ends within a comment. That's not so
bad. However, since the text following up to the next */ will be
considered to be in a comment,
5 matches
Mail list logo
