print_r and large arrays

[meltedown]

Normally, if I use
$result=print_r ($array,TRUE);
print_r prints nothing and $result is equal to the readable array.

However, if $array is very large, print_r prints the array and returns
nothing.

Is this correct ? I don't see anything about this in the the manual.

I have tried limiting the size to array to see exactly how large the
array has to be to trigger this behavior, but the exact size seems to be
variable or it depends on some other factor. Can anyone explain what is
the deciding factor ?

[Carl Vondrick]

Re: print_r and large arrays

meltdown wrote:[color=blue]
> Normally, if I use
> $result=print_r ($array,TRUE);
> print_r prints nothing and $result is equal to the readable array.
>
> However, if $array is very large, print_r prints the array and returns
> nothing.
>
> Is this correct ? I don't see anything about this in the the manual.
>
> I have tried limiting the size to array to see exactly how large the
> array has to be to trigger this behavior, but the exact size seems to be
> variable or it depends on some other factor. Can anyone explain what is
> the deciding factor ?[/color]
You can use output buffering to get around this.

Just do:

ob_start();
print_r($array) ;
$value = ob_get_flush(); // or something like that!

I'm not sure why your problem is happening, but have you checked memory?
I bet it is a memory issue.

--
Carl Vondrick

https://www.carlsoft.net

usenet [at] carlsoft [dot] net

[meltedown]

Re: print_r and large arrays

Carl Vondrick wrote:[color=blue]
> meltdown wrote:[color=green]
>> Normally, if I use
>> $result=print_r ($array,TRUE);
>> print_r prints nothing and $result is equal to the readable array.
>>
>> However, if $array is very large, print_r prints the array and returns
>> nothing.
>>
>> Is this correct ? I don't see anything about this in the the manual.
>>
>> I have tried limiting the size to array to see exactly how large the
>> array has to be to trigger this behavior, but the exact size seems to
>> be variable or it depends on some other factor. Can anyone explain
>> what is the deciding factor ?[/color]
> You can use output buffering to get around this.
>
> Just do:
>
> ob_start();
> print_r($array) ;
> $value = ob_get_flush(); // or something like that![/color]

OK thanks.[color=blue]
>
> I'm not sure why your problem is happening, but have you checked memory?
> I bet it is a memory issue.
>[/color]

I assum you mean memory on the server. How do I check that ?

[Carl Vondrick]

Re: print_r and large arrays

meltedown wrote:[color=blue]
> I assum you mean memory on the server. How do I check that ?[/color]

The best way is to use SSH and run the top command. This will display
the process information.

If you do not have SSH access, then try this:

http://www.php.net/manual/en/function.memory-get-usage.php

--
Carl Vondrick

https://www.carlsoft.net

usenet [at] carlsoft [dot] net