First, you need to understand my original question. I came here not to ask
for help on figuring the problem. I came here to ask for information of
other compilers. (Look at the topic of this email.) It was when the list
member asking me what problems I encountered, I started telling them what
happened.

You said I should have posted the code here. Did you know that I have
offered twice to post the code here if someone is interested? But no one
responded to that. I wanted to know someone wants to see the code before I
post because it involves work. And I have current projects to do.

My original version was erased when I installed a later version, therefore I
cannot compile the code to view the assembly. And even I can see there is a
problem, I didn't tell me more than I already knew. What I really need to
know is if it has been fixed. Only the technical support can answer. I took
the advice of a member to contact the technical support. And it was a
courtesy on my part to update the members what happened. And I can update
you that we are working together now to narrow the problem.

It seems that when someone's advice is not being followed, "pressure builds
up" and it's OK for him to attached personally. But you know what? That
person is actually building pressure, too. Now, is OK to counter-attack
personally?



----- Original Message -----
From: "D. Jay Newman" <jay@SPRUCEGROVE.COM>
To: <PICLIST@MITVMA.MIT.EDU>
Sent: Friday, August 15, 2003 1:46 PM
Subject: Re: [PIC]: Seek C Complier Recommendations


> > I don't value personal attacks on the PICLIST, it doesn't matter that
they
> > are directed at someone else. Just because you "form an opinion of other
> > people" doesn't mean you shouldn't hit delete rather than reply in an
> > offensive manner.
>
> I'm also trying not to be judgemental, but Olin has a point. The OP said
> there was a bug, Olin told him how to demonstrate the bug, the OP
> continued claiming vague theories.
>
> I don't like personal attacks also, but sometimes the pressure just
> builds up too much.
>
> If there really is a bug, the OP should make a simple test-case, and
> post the C code and the generated assembly. Then the list could actually
> help him find the problem rather than wasting our time guessing. Having
> information really does make an argument more fun.  :)
> --
> D. Jay Newman          !
> jay@sprucegrove.com    ! Xander: Giles, don't make cave-slayer unhappy.
> http://enerd.ws/~jay/  !
>
> --
> http://www.piclist.com hint: PICList Posts must start with ONE topic:
> [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads