Bug#466637: bisonc++: package description seems made wrong references (debian/control)

2008-02-26 Thread Frank B. Brokken 
Dear Felipe Augusto van de Wiel (faw), you wrote:
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Package: bisonc++
 Version: 2.4.1-1
 Severity: wishlist
 Tags: patch
 
 
 Hi,
 
   While translating the bisonc++ package description in
 DDTP, I had the impression that some wrong references are made
 about bison++ and bisonc++. Below is a proposed patch, but I'm
 a little bit unsure if that is the intended idea. I hope this
 helps.

Thank you for your e-mail about Bisonc++.

Your observation helps, and you're right. I'll include your repair in the next
release.

Thanks for your contribution,

Cheers,

[Cc: Tony Mancill, George Danchev]

-- 
Frank B. Brokken
Center of Information Technology, University of Groningen
(+31) 50 363 9281
Public PGP key: http://pgp.surfnet.nl:11371/
Key Fingerprint: 8E36 9FC4 1DAA FCDF 1A0D  B19F DAC4 BE50 38C6 6170


signature.asc
Description: Digital signature

Bug#466637: bisonc++: package description seems made wrong references (debian/control)

2008-02-19 Thread Felipe Augusto van de Wiel (faw) 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: bisonc++
Version: 2.4.1-1
Severity: wishlist
Tags: patch


Hi,

While translating the bisonc++ package description in
DDTP, I had the impression that some wrong references are made
about bison++ and bisonc++. Below is a proposed patch, but I'm
a little bit unsure if that is the intended idea. I hope this
helps.

- --8--8--8--8--8--
- --- control.orig2008-02-20 01:00:32.417542772 -0300
+++ control 2008-02-20 01:01:56.422329932 -0300
@@ -23,13 +23,13 @@
  function. The class can easily be provided with additional members without
  needing polymorphic functions. Consequently, classes generated by bisonc++
  have no virtual members and actually have but one public member: parse(),
- - replacing the old-style bison and bisonc++ yyparse() function.
+ replacing the old-style bison and bison++ yyparse() function.
  .
  Bisonc++ offers many options, among which an option to define classes
  generated by bisonc++ in a separate namespace. This allows developers to
  define additional symbols, even outside of the class generated by bisonc++,
  without encountering name-collision problems. With bisonc++, artificial means
- - to prevent name-collisions, like bison and bisonc++'s yy-convention are not
+ to prevent name-collisions, like bison and bison++'s yy-convention are not
  required anymore when using bisonc++.  Bisonc++ merely generates C++ code. If
  C code is required, bison should be used. Bisonc++'s grammar requirements are
  highly compatible with bison's requirements, so converting a bison grammar
- --8--8--8--8--8--

Thanks in advance.


- --- System information. ---
Architecture: i386
Kernel: Linux 2.6.22-3-686

Debian Release: lenny/sid
500 testing www.debian-multimedia.org
500 testing security.debian.org
500 testing ftp.br.debian.org

- --
Felipe Augusto van de Wiel (faw)
Debian. Freedom to code. Code to freedom!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHu6aECjAO0JDlykYRAnwsAJ9i+Ggo+kx4p/fL2xds4o945f6jMwCgoE4S
+RruXKKOrmTHUNNj1PAJqz4=
=K7x5
-END PGP SIGNATURE-



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