Hey,
I was just thinking about to remove the configure checks for e.g. strstr() or fgetpos() as these seem to be defined in the C89 standard (according to their manpages on a Debian system).
I don't think we need to support any platforms which not even provide a C89 compatible C library as probably Glib and GTK aren't available on such platforms at all.
Furthermore, we already use strstr() in the Geany code without checks and Scintilla uses strstr() also without checking.
And I'm not sure about the check for stdlib.h. Are there systems where stdlib.h might not be available? At least is GLib and GTK available on these systems?
According to http://svn.gnome.org/viewvc/glib/trunk/configure.in?revision=6955&view=m..., GLib doesn't seem to check for strstr() and stdlib.h. So why should we?
What do you think?
Regards, Enrico
On Sun, 8 Jun 2008 09:50:22 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
According to http://svn.gnome.org/viewvc/glib/trunk/configure.in?revision=6955&view=m..., GLib doesn't seem to check for strstr() and stdlib.h. So why should we?
I don't know much about portability, but probably it's fine to do the same as GLib does. Especially if GLib 2.6 does it (I haven't checked though).
Regards, Nick
On Mon, 9 Jun 2008 15:21:01 +0100, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Sun, 8 Jun 2008 09:50:22 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
According to http://svn.gnome.org/viewvc/glib/trunk/configure.in?revision=6955&view=m..., GLib doesn't seem to check for strstr() and stdlib.h. So why should we?
I don't know much about portability, but probably it's fine to do the same as GLib does. Especially if GLib 2.6 does it (I haven't checked though).
The configure.in of the GLib 2.6 branch[1] actually has a check for stdlib.h. So, to stay safe we could keep it, too. At least we won't break anything which could have worked before. Anyway, the strstr() check can be removed, IMO.
[1] http://svn.gnome.org/viewvc/glib/tags/GLIB_2_6_0/configure.in?revision=3533&...
Regards, Enrico