Geek asks and answers

Why does Objective-C have native autoconf support?

Clearly, C, C ++ and Fortran are classic GNU languages ​​and have full support. I know that Erlang was added because the Erlang community has been very careful in adding this functionality to autotools, but what about Objective-C? I think that it was supported for a long time (I vaguely recall that it was supported in the early 2000s, long before the last iStuff explosion). Was it because the guys, thanks to NeXTstep, worked so hard for him?

I read Calcote’s excellent Autotools book and they bring up the history of auto-tunes. It always seemed strange to me that Objective-C had such strong support in GNU tools, given its (until recently) low use.

+3
source share
2 answers

Objective-C support in the GCC toolchain dates from at least 1988. NeXTSTEP comes with a bunch of random FSF / GNU related tools, almost all of which have been configured with help autoconffrom the start.

Support for IIRC, Objective-C in the GCC software chain has preceded autoconf for several years.

Objective-C has always been very enthusiastic about a number of neck-god groups of the 90s (i.e. those of us who choose not to program Windows or Mac OS). In fact, Objective-C and C ++ are about the same age.

Oh, and ....

Go to my lawn.

:)

+5
source

GNUStep and WindowMaker are pretty old GNU projects using Objective-C ...

+1
source

More articles:


All Articles