Another dumb question, maybe..
Is it possible to manage errors from directory and file related functions
in such a way that they can be displayed as part of the page markup and
not splattered all over, or displayed instead of content?
I am aware of the use of @ to suppress these types of errors, but they
will also not be logged. So I write error messages that are returned in an
organized manner and can be displayed. If I get them I am not necessarily
able to discern the nature of the error. E.G. a file isn't written because
a: the directory doesn't exist,
b: the directory doesn't have write permission set correctly
c: something was wrong on the read side and the string that the file
contents are supposed to be in is empty ( the file size was not set
because there was something wrong with the file reference on fread)
I have been adding more and more tests for these details, but there has to
be a limit somewhere.