X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
Date:	Tue, 19 May 2015 13:05:07 -0400
Message-Id:	<201505191705.t4JH57E8010700@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	djgpp AT delorie DOT com
In-reply-to:	<op.xyvgdewswhxjl4@localhost> (fork@lllljunkqwer.cpm)
Subject:	Re: ANNOUNCE: DJGPP 2.05 beta 1
References:	<201505042003 DOT t44K3odg011007 AT delorie DOT com>
	<55501DAD DOT 1080604 AT iki DOT fi>
	<CAA2C=vAvMW-yquZLSN=Z39NU24Kqf7urjan90801i7BDTdqOvQ AT mail DOT gmail DOT com>
	<55579278 DOT 8090301 AT iki DOT fi>
	<CAA2C=vBaQKzmch_buxFm20DJLcG+zv6d6803+qMEx=baA4Frog AT mail DOT gmail DOT com>
	<555829A6 DOT 8010502 AT iki DOT fi>
	<CAA2C=vA73qPvoDFytp3FeW6bCD1-XuGsFFoDinoKn2KYY1fkow AT mail DOT gmail DOT com>
	<555870E8 DOT 7040302 AT iki DOT fi>
	<CAA2C=vDhD6BJj89o1i0FRd2U0H4bTpGGN4zH6qs7FJKxzqhuQg AT mail DOT gmail DOT com>
	<201505180114 DOT t4I1EiaX017288 AT delorie DOT com>
	<CAA2C=vCyrQ_+Yq6XsRD-UO4r=j9WoGGiXoqQFrkbiEQpzX+=MA AT mail DOT gmail DOT com>
	<201505181216 DOT t4ICGaKO014123 AT delorie DOT com>
	<CAA2C=vCk5MY74z+HNVzzdLByg71Y_9ObK-1jPxJ_KF8eqRDZMQ AT mail DOT gmail DOT com>
	<83zj52dkns DOT fsf AT gnu DOT org>
	<CAA2C=vAPcN+MKC_2tcZqVmo9gvF2Cxdo+K+-qfKaNrQuCkMnEw AT mail DOT gmail DOT com>
	<83wq05eukk DOT fsf AT gnu DOT org>
	<CAA2C=vBKihqvw152LsGvWEiSei7TczN6Vmxsvebtnoz_E5=u4g AT mail DOT gmail DOT com>
	<83twv9espx DOT fsf AT gnu DOT org>
	<CAA2C=vC8ge-O+yDkTeXf351E+bpURkxOGmvdp19JTMnCjfkZbA AT mail DOT gmail DOT com>
	<83siater66 DOT fsf AT gnu DOT org> <op DOT xyvgdewswhxjl4 AT localhost>
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Sigh, here we go again with Eli ...

Sigh, here we go again with Rod ...

> However, you eventually respond this way to *EVERYBODY* ...

I re-read the thread, and Eli asked a perfectly valid (if unexpected)
question, and rather than respect the question, the OP disrespected
the poster.  Given that the issue is complex and yet still not fixed,
suggestions for the rare-but-possible cases are justified.  The only
people who should be insulted by such suggestions are those who have
already solved the problem, or already tried the advice indicated, not
those who are still trying to figure it out.

We've seen a lot of wierd bugs in the past, so if we suggest something
completely out of the blue, it's probably because it's happened
before.

> rudely

So you see it.  I don't.

> ask them if they're sure

Or, in this case, if they've considered the case where the compiler
might be lying to them about what it's doing.

> after they just spent a huge amount of time understanding the issue.

Yet still not solving.

> perception of others which is abnormal?  ...  D.J. and Charles seem

If you've been around all this time, why don't you spell my name
correctly yet?  "I'm insulted, and assume you're doing it on purpose
just to annoy me[*]."  Take the time to be precise in what you write,
and consider all the ways it can be read, and perhaps you'll have less
conflict with people who don't know you.  It's a lesson I've learned
the hard way over the decades.  Heck, I can't even tell when my
brother is joking in an email, and I've known him all his life.

[*] I'm not insulted, I assume you're innocently mistaken, just using
    it as an example of how people can mis-read others' posts.

> to be the only people who haven't taken offense at one time or another
> to you in all that time, but you don't respond that way to them, even
> when D.J. has no knowledge of the issue at hand.

I've gotten all sorts of responses from Eli.  Often, he's right.  He's
earned the right to suggest stupid things to me, because sometimes the
stupid is on my side.

Also, I've learned to look at conversations from the other point of
view, in case it's just a misunderstanding or miscommunication.
Remember, Eli's native language is *not* English, despite how well he
speaks it.

> HTH,

It doesn't.

- Raw text -