Re: [Python-Dev] Notice of intent: rich comparisons
David Beazley writes:
Maybe I'm just lucky, but I've written nothing but ANSI C for the last 8 years and have never had a problem compiling it on any machine. I don't see this as being a huge issue.
Wasn't SunOS 4.x the problem child here? There are still a lot of people using these systems, for reasons that aren't clear to me. (Did support for some older hardware get dropped? Sounds like the most reasonable reason to use the old OS is legacy hardware.) -Fred -- Fred L. Drake, Jr. <fdrake@acm.org> Corporation for National Research Initiatives
"Fred" == Fred L Drake <fdrake@cnri.reston.va.us> writes:
Fred> Wasn't SunOS 4.x the problem child here? There are still Fred> a lot of people using these systems, for reasons that aren't Fred> clear to me. (Did support for some older hardware get Fred> dropped? Sounds like the most reasonable reason to use the Fred> old OS is legacy hardware.) There might be, but the bundled compiler in SunOS 4 was never intended to be used for anything more than recompiling the kernel. Years ago, I had conversations with Sun engineers who claimed that no bug in the bundled compiler was ever fixed unless it directly impacted on kernel rebuilds. Even back then they recommended using something other than the bundled crufty old K&R compiler for building all other stuff, and this was when there was that huge hoopla over the unbundling of the compiler. SunOS 4 users can probably be mostly satisfied with gcc. -Barry
Barry A. Warsaw writes:
There might be, but the bundled compiler in SunOS 4 was never intended to be used for anything more than recompiling the kernel. Years ago, ... SunOS 4 users can probably be mostly satisfied with gcc.
Barry, This is good enough for me. I'd certainly rather avoid K&R C! -Fred -- Fred L. Drake, Jr. <fdrake@acm.org> Corporation for National Research Initiatives
Barry> SunOS 4 users can probably be mostly satisfied with gcc. Fred> This is good enough for me. I'd certainly rather avoid K&R C! Besides, aren't there tools available that can strip most of the ANSI-ness out of ANSI C? (Un)Protoize? For those (few?) people who are really still stuck using a K&R compiler I would think those tools, perhaps supplemented with some patch files maintained outside the main Python source tree, would be sufficient. Skip Montanaro | Mojam: "Uniting the World of Music" http://www.mojam.com/ skip@mojam.com | Musi-Cal: http://www.musi-cal.com/ 518-372-5583
"skip" == <skip@mojam.com> writes:
skip> Besides, aren't there tools available that can strip most of skip> the ANSI-ness out of ANSI C? (Un)Protoize? I think so. Seems I have unprotoize already; probably got it for free with gcc, or some other GNU tool. -B
Besides, aren't there tools available that can strip most of the ANSI-ness out of ANSI C? (Un)Protoize? For those (few?) people who are really still stuck using a K&R compiler I would think those tools, perhaps supplemented with some patch files maintained outside the main Python source tree, would be sufficient.
I mentioned ansi2knr.c in an earlier post. It's a small utility, and can be distributed with the Python core (it's GPL'd, but since it isn't linked with Python, that's not a problem). this is used by ghostscript and the ijg jpeg library, among others: ftp://ftp.cs.wisc.edu/ghost/ansi2knr.c (or via http://www.cs.wisc.edu/~ghost/) Cheers /F fredrik@pythonware.com http://www.pythonware.com
participants (4)
-
Barry A. Warsaw -
Fred L. Drake -
Fredrik Lundh -
skip＠mojam.com