Re: A Problem With GD
- From: Mark Manning <markem@xxxxxxxxxxx>
- Date: Sun, 05 Mar 2006 15:06:34 -0600
A. Sinan Unur wrote:
Mark Manning <markem@xxxxxxxxxxx> wrote in
news:1208qpaie24bgae@xxxxxxxxxxxxxxxxxx:
A. Sinan Unur wrote:
You might be missing the point of UseNet: When I have a
question/issue, I find a group where my question is relevant, and
then post it to receive any feedback anyone on that group can give.
Well, the reason I posted to comp.lang.perl.misc was beause there
isn't a comp.lang.gd or anything like that.
I am not saying comp.lang.perl.misc was the wrong place to post your question, although comp.lang.perl.modules might have been more appropriate.
That - is probably true.
When you post on comp.lang.perl.misc, you are expected to post code that is strict and warnings clean, and others can run with little effort.
Only - if you are looking for help. My original post did not say I was looking for help. It said:
"I believe I may have uncovered a problem with the GIF renderer under GD...."
Not
"I need help with GD."
Each group has its own rules. As I try to stay away from the alt.* hierarchy, it is not hard to find out what those rules are and follow
them.
c.l.p.m. also has rules. One of those is that you need to provide
enough information with your post. IMNSHO, that is especially true
when you are blaming mistakes in the code on imagined defects in
someone else's library in a public forum.
Your first mistake was thinking I was asking for help. Your second is in thinking I was "blaming mistakes". It never said "I KNOW I've found a problem" or "There IS a problem" it said:
"I BELIEVE I MAY HAVE uncovered a problem..."
You jumped the gun. Not once but several times.
A neutral question would have been: "How do I get in touch with the author of libgd or the author of GD.pm?" with no extranous claims of bugs in either library.
Well, that may be a better way of doing it, but my way has always been to lead in with what it is I am thinking. Which was what I posted. The person who e-mailed me did point me in the direction of Mr. Stein's web page. I am presently attempting to track down the bug in Mr. Boutell's source code. If I can find it I will submit the bug back to him so it can be removed. The hint in the problem which I posted is that there is one off-color dot for every four dots. Which means (to me) that the GIF section is using an 8bit word while the truecolor software uses a 32bit word. Therefore, even though the truecolor flag has already been set - it is being ignored somewhere in the code and that code is overwritting the truecolor image thinking that it is writing out GIF (or 8bit) information into the image.
Incidentally, those questions are trivially answered by a two second Google or CPAN query, so what is the point of asking thousands of people around the world to do that for you?
Again - you state that I am asking a question. Yet, above you recognize that maybe I am correct in my assertion that I was not looking for help. Which side are you going to be on? Either I was asking for help or I was looking for someone.
A statement that raises the possibility of a bug requires a test case that replicates the behavior.
Yes, that is correct. Mr. Stein has already tested the program I sent and informed me that the GD.pm package is not where the error is located. Which is why I am concentrating on Mr. Boutell's code.
In that case, how can you make the claim that there is a bug in
GD.pm?
As I have said before. The code that was posted was thrown together
and it gave the results it gave. That code is not THE code I am
working on but as quickly reduced and posted as I could after I'd
decided to go ahead and do it. My mistake - is in posting the code.
No, your mistake is not posting code in the first place. Anyone who might be willing to help you will need to be able to replicate the behavior.
No - it definitely was a mistake. I've already tracked down yet another problem with the code which I will be including in my final write-up to Mr. Boutell.
Your second mistake is posting code that was not strict and warnings clean.
No - my mistake was just posting the code.
Your third mistake was to call me an ass for trying to teach you how to write code so you can eliminate the possibility of bugs in your *own* code before claiming a bug in a library.
And what if I did not want you to "teach me" anything? Yet, when I first said "no thanks" to you - you continued to try to cram down my throat your special "teachings". Something forced onto someone else is not something that person will thank you for.
By the way, you seem to have a fascination with rear-ends? Why do you
have to mention them every few words? Could you stop cursing maybe?
It was in response to what you were saying - as you well know.
Oh, I see ...
No. I don't think you really do as is obvious by your previous postings.
"A. Sinan Unur" <1usa@xxxxxxxxxxxxxxxxxxx> wrote in news:Xns9775C5C9B6F93asu1cornelledu@xxxxxxxxx:
Right margin comments that wrap are silly and annoying.
Give your variables meaningful names, and declare them in the smallest applicable scope so you don't have to resort to comments
to remember what they do.
**That** justifies you calling me an ass?!
No - try this:
"Not posting warnings and strict clean code is considered *very* rude
here. So, here's a piece of my mind before I wrestle through your code."
I did not ask you to "wrestly through your code" - nor to give me a piece of your mind - you asked me:
"How can anyone else reproduce the error if you do not provide a short but
complete script that generates the behavior you see?"
I didn't care if you could reproduce the error but as I've said I went "whatever" and provided a short, but complete script and you then said:
"It looks like you haven't read the posting guidelines yet. Please do."
Followed by the rest that went downhill from there.
I DARE you to ...
*Sigh*
I am sure everyone else has had enough of this. So, bye.
Ah. So you couldn't find anywhere that I said anyone had to conform to my way of doing things. You can only do that if you cut up whatever I've posted and change it around to fit your outlook. Which IS that you want everyone to conform to your way of doing things.
I believe you are beginning to realize that what you did was not a very nice thing to do. Believe me when I say I worked at a help desk for years at college and some of the people who worked there began acting like you have acted here. It happens. You answer hundreds and thousands of questions. Many repetitious, many you ask yourself why they even bothered to come to you they know so little or get everything wrong. The trap is allowing yourself to begin treating everyone like they are morons or that you are better than they are. Especially when you have no idea who that other person really is.
Sinan
Heh. I already know this isn't going to be the last message.
.
- Prev by Date: Re: A Problem With GD
- Next by Date: Re: Different results parsing a XML file with XML::Simple (XML::Sax vs. XML::Parser)
- Previous by thread: Re: A Problem With GD
- Next by thread: Re: A Problem With GD
- Index(es):
Relevant Pages
|
Loading
