> > Another example is touch(). It requires utime which I assume all
> > OS's have although I don't know. And if not I assume PHP might
> > essentially say "No utime huh? Let's use mtime/atime/ctime instead
> > and define HAVE_UTIME as true." Again, I don't know this topic of
> > utime so am
> I think this information should be individualized per function. Each
> would mention the conditions that need to be met, and why it may not
> be met. Having one entity for this will only scare the user and force
> extra work on those who will have it available. I am guessing that
> some of the
Another example is touch(). It requires utime which I assume all
OS's have although I don't know. And if not I assume PHP might
essentially say "No utime huh? Let's use mtime/atime/ctime instead
and define HAVE_UTIME as true." Again, I don't know this topic of
utime so am only guessing here.
I think this information should be individualized per function. Each
would mention the conditions that need to be met, and why it may not
be met. Having one entity for this will only scare the user and force
extra work on those who will have it available. I am guessing that
some of these condit
Some functions are system-dependent in that if they're not detected at
compile time, they won't be included in PHP. Currently the
documentation does not tell the user any information about this type
of function availability and could cause some confusion when a user
tries to use a function and it s
