#C Compilers: which one?
5 messages in this thread
I always advise a dieter not to enter a bakery, Ethan.
I advise parents with children to not own a gun.
I advise Marital Artists to stay away from bars and dark alleys.
And I advise C programmers to stay away from compiler(s) that offer ilac.
We all get in situations where we do what's convenient. If it's not convenient,
we won't do it. Currently, the Lattice environment offers a superior compiler,
and no temptation to screw up using ilac. That makes it a clear winner, in my
mind.
–Ben-
Ah Ben, but there are those of us who have will-power and vision. We know that
when using ILAC we run the risk of producing non-portable code (or run the
certainty), but we know waht we're doing. There are times when a quick hack
serves its purpose – prototyping comes to mind, or just fooling around with
ideas. Naturally production code should avoid ILAC, but there's no reason to
not to experiment with it.
Dave @OTG
Um. Yeah. sorta. If you never let it out the door, never use it in production
work, and never show it to a fledgling programmer, maybe so. Maybe.
–Ben-
Ben,
a potentially fatal flaw in your argument. I comment EVERYTHING. I never
assume that I will understand what the heck I was doing even a month later. In
such an environment, ILAC is not much of a hazard. True, I could put it in a
seperate module, if I want'ed to go to the extreme legnths required, and no
matter what you say, they can get extreme. I choose to use the ILAC method, if
it is called for. Are you saying that you don't use comments? If so, you are
violating the first rule of programming.
Brian J. Bartlett
Brian,
You may be able to understand your ILAC, but heaven forbid that you have to
move your code to another compiler. Ben is largely correct. ILAC serves
relatively little purpose in production code.
Dave @OTG