Hello Andrey,
Thursday, May 20, 2004, 8:15:41 PM, you wrote:
> Sara Golemon wrote:
I hope that everyone will be happy with this. var_dump() is still BC
>>
>> since
>>
it does not print ":public" on public properties.
>>>
>>>Fine with me. I'm not sure printing public is a bad idea.
Sara Golemon wrote:
I hope that everyone will be happy with this. var_dump() is still BC
since
it does not print ":public" on public properties.
Fine with me. I'm not sure printing public is a bad idea. How many ppl
actually use this in their application for purposes other than debugging?
I sure ho
> >I hope that everyone will be happy with this. var_dump() is still BC
since
> >it does not print ":public" on public properties.
> >
> Fine with me. I'm not sure printing public is a bad idea. How many ppl
> actually use this in their application for purposes other than debugging?
>
I sure hope n
On Thu, 20 May 2004, Jan Schneider wrote:
> Zitat von Andi Gutmans <[EMAIL PROTECTED]>:
>
> > I'm OK with adding it to print_r() too if no one has any serious objections.
>
> Perhaps only for members explicitely declared public, as opposed to
> var-style properties.
We can't distantiate between t
Zitat von Andi Gutmans <[EMAIL PROTECTED]>:
I'm OK with adding it to print_r() too if no one has any serious objections.
Perhaps only for members explicitely declared public, as opposed to
var-style properties.
At 12:04 PM 5/20/2004 +0200, Derick Rethans wrote:
On Thu, 20 May 2004, Andi Gutmans wro
I'm OK with adding it to print_r() too if no one has any serious objections.
At 12:04 PM 5/20/2004 +0200, Derick Rethans wrote:
On Thu, 20 May 2004, Andi Gutmans wrote:
> Fine with me. I'm not sure printing public is a bad idea. How many ppl
> actually use this in their application for purposes oth
On Thu, 20 May 2004, Andi Gutmans wrote:
> Fine with me. I'm not sure printing public is a bad idea. How many ppl
> actually use this in their application for purposes other than debugging?
Well, print_r doesn't print it either; so IMO if we add public here, we
need to do that for print_r too.
r
Fine with me. I'm not sure printing public is a bad idea. How many ppl
actually use this in their application for purposes other than debugging?
At 09:28 AM 5/20/2004 +0200, Andrey Hristov wrote:
Andi Gutmans wrote:
At 11:42 AM 5/18/2004 +0200, Christian Schneider wrote:
Sara Golemon wrote:
var_d
Andi Gutmans wrote:
At 11:42 AM 5/18/2004 +0200, Christian Schneider wrote:
Sara Golemon wrote:
var_dump($someobject); shows only public properties (as I'd expect), but
print_r($someobject) shows all properties (explicitly identifying
protected/private props).
I agree with Derick and Andrey in tha
At 11:42 AM 5/18/2004 +0200, Christian Schneider wrote:
Sara Golemon wrote:
var_dump($someobject); shows only public properties (as I'd expect), but
print_r($someobject) shows all properties (explicitly identifying
protected/private props).
I agree with Derick and Andrey in that if anything should
On Tue, 18 May 2004, Sara Golemon wrote:
> The next question that brings up then is in relation to bug#27798:
>
> I would think that get_object_vars() should expose private/protected props
> when called from within the class itself (as appropriate based on
> inheretance of course). Is this assum
> var_dump($someobject); shows only public properties (as I'd expect), but
> print_r($someobject) shows all properties (explicitly identifying
> protected/private props).
>
So, to sum up the responses to the above question:
1) It's okay for print_r/var_dump to expose public/protected members (thei
Derick Rethans wrote:
I don't want var_dump() to change.
Oops, sorry for being too brief, I meant I agree with you about print_r
being alright and like Andrey I think *if* something's changed it should
be var_dump ;-)
- Chris
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe
On Tue, 18 May 2004, Christian Schneider wrote:
> Sara Golemon wrote:
> > var_dump($someobject); shows only public properties (as I'd expect), but
> > print_r($someobject) shows all properties (explicitly identifying
> > protected/private props).
>
> I agree with Derick and Andrey in that if anyth
Sara Golemon wrote:
var_dump($someobject); shows only public properties (as I'd expect), but
print_r($someobject) shows all properties (explicitly identifying
protected/private props).
I agree with Derick and Andrey in that if anything should be changed it
is var_dump.
Reasoning: PPP is there to
15 matches
Mail list logo
