On Thursday, March 28, 2002, at 07:34 PM, bvr wrote:
> not really ambiguous,
(actually, that's what I was saying, that they are -less- ambiguous, and
more specific, but no big deal on that little matter).
> and I think these functions being flexible enough to handle other
> resource types can hardly be seen as a disadvantage..
Every time I try to use one of these functions, I get an error message
from my browser (not from PHP) that the attempt to load the URL failed.
Is this a sign of running into memory problems? If so, what can I do
about it? It seems that the only file-reading function that doesn't
create this error message in my script is fgets(), but as soon as I try
to implode the lines I pulled with fgets() into one string, I get the
error message again. In other words, every time I try to pull my XSL
file into my script, it happens.
(I would not have imagined I would run out of memory b/c I have php.ini
set to 16M per script and the XSL file is only 8kB, though the script
does do a lot of things.)
Anybody know what's going on here?
Web Developer Temp
Media Lab, H.H. Brown
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php