Re: Bug#3253: Pine base64 bug
Hi,
>>"James" == James Troup <J.J.Troup@comp.brad.ac.uk> writes:
James> So you don't think a man that trashed your harddisk (if that
James> were documented and intended behaviour) would be a bug? What
James> then, pray tell, is it? Good, correctly-written and bug free
James> software?
Nope. Not a bug. (mke2fs does just that, and I don't call it a
bug). Documented and intended.
James> I don't see what is so holy and almighty about documenting
James> something and claiming it's intended. Documenting something
James> broken doesn't make it any less broken. Something that's
James> broken, but was intended by the author is no less broken.
Now, this is about who gets to decide what a program should
do? I think the author has the right to say what his program does and
code that. You can't tell the author that what he elected to write is
broken. You don't like it, roll your own. Or don't use the software.
This is like religion. Who knows the one true non-broken way?
manoj
who really hates what pine does
--
"... You're damned if you do, and damned if you don't." "But that's
not *fair*!" "Of course it's not fair. We're *evil*. Look it up."
Manoj Srivastava <url:mailto:srivasta@acm.org>
Mobile, Alabama USA <url:http://www.datasync.com/%7Esrivasta/>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: