FUDforum: comp.lang.php » Operator precedence

Home » Imported messages » comp.lang.php » Operator precedence

Show: Today's Messages :: Polls :: Message Navigator

Re: Object constructors/destructors [message #185149 is a reply to message #185147]

Sun, 02 March 2014 20:42

Jerry Stuckle
Messages: 2598
Registered: September 2010

Karma:

Senior Member

On 3/2/2014 2:28 PM, Richard Damon wrote:
> On 3/1/14, 2:22 PM, Jerry Stuckle wrote:
>> On 3/1/2014 12:56 PM, Richard Damon wrote:
>>> On 2/27/14, 8:25 AM, Jerry Stuckle wrote:
>>>> On 2/26/2014 11:49 PM, Richard Damon wrote:
>>>> > On 2/26/14, 8:44 AM, Jerry Stuckle wrote:
>>>> >> On 2/26/2014 7:50 AM, Richard Damon wrote:
>>>> >>>
>>>> >>> An the "name" of the Deserializing constructor in PHP is __wakeup().
>>>> >>>
>>>> >>> You also do NOT get two destructor calls on the same object, the
>>>> >>> deserializing created a new object.
>>>> >>>
>>>> >>
>>>> >> __wakeup() is not a constructor - and does not do the same thing.
>>>> >>
>>>> >
>>>> > What makes it NOT a constructor? IT seems to be exactly the thing that
>>>> > does what you say must be done to make the new object via
>>>> > unserialization.
>>>> >
>>>>
>>>> If you want to consider __wakeup() to be a constructor, then you must
>>>> consider __sleep() to be a destructor. In that case, PHP is also wrong
>>>> because if an object is serialized, it will call both __sleep() and the
>>>> destructor. This would be two calls to destructors for the same object.
>>>>
>>>
>>> WHY does __sleep() need to be a destructor?
>>>
>>> __sleep() is a function to control how an object is serialized, and the
>>> object, as you seem to know, still exists, so no destructor should
>>> happen at this point, in fact, if you look at it, __sleep() has not
>>> expected to have any effect on the current object, its purpose is to
>>> make sure that __wakeup() will get all the data it needs, and allow the
>>> removal of data that it won't need.
>>>
>>
>> If you are going to claim __wakeup() is a constructor, then you have to
>> agree that it's opposite (__sleep()) is a destructor. Otherwise you are
>> being inconsistent.
>>
>> You can't just make up rules as you see fit!
>>
>
> Then why are you claiming that something that isn't a desturctor must be
> one.
>

I'm not - you're the one claiming __wakeup() is a constructor, but it's
opposite, __sleep() is not a destructor.

> Serialization, creates an external representation for an object, that is
> what __sleep() is part of. This does NOT inherently involve the
> destruction of the object (at least at that point).
>

Then __wakeup() does NOT inherently involve creation of an object.

> Deserialization, on the other hand, creates an object from an external
> representation. so it will involve the construction of a new object (you
> can do "in-place" deserialization in some languages, where you first
> create a dummy object, and then fill it in with the external data, but
> this is normally a clumsy way to define it).
>

Not in other languages. It builds from an already existing object where
the constructor has been called.

> Note that the object oriented paradigm does have asymmetry in it. A
> given type will tend to have multiple constructors, for the different
> ways that an object might come into existence. There is usually only one
> destructor. In PHP, one of these constructors is called __construct()
> which is the general purpose constructor. (unlike in other statically
> type languages, we can only define one of these). PHP also lets us
> define a piece of the deserialing constructor with __wakeup() (PHP does
> some of the heavy lifting here in parsing the serialized data and
> setting up the object, __wakeup() is just required to do any final
> needed operations after the values have been set.)
>

Constructors are constructors, and the destructor is a destructor. No
asymmetry there. Except in PHP.

--
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex(at)attglobal(dot)net
==================

Report message to a moderator

[Message index]

		Operator precedence By: Christoph Michael Bec on Sun, 23 February 2014 17:03
		Re: Operator precedence By: GS on Sun, 23 February 2014 19:42
		Re: Operator precedence By: Christoph Michael Bec on Sun, 23 February 2014 20:23
		Re: Operator precedence By: Jerry Stuckle on Sun, 23 February 2014 21:34
		Re: Operator precedence By: Richard Damon on Sun, 23 February 2014 23:36
		Re: Operator precedence By: Jerry Stuckle on Mon, 24 February 2014 02:09
		Re: Operator precedence By: Ben Bacarisse on Mon, 24 February 2014 04:49
		Re: Operator precedence By: Thomas 'PointedEars' on Mon, 24 February 2014 11:56
		Re: Operator precedence By: Christoph Michael Bec on Mon, 24 February 2014 16:38
		Re: Operator precedence By: Ben Bacarisse on Mon, 24 February 2014 21:25
		Re: Operator precedence By: Thomas 'PointedEars' on Mon, 24 February 2014 23:38
		Re: Operator precedence By: Christoph Michael Bec on Tue, 25 February 2014 00:07
		Re: Operator precedence By: Thomas 'PointedEars' on Tue, 25 February 2014 00:37
		Re: Operator precedence By: Christoph Michael Bec on Tue, 25 February 2014 01:12
		Re: Operator precedence By: Thomas 'PointedEars' on Tue, 25 February 2014 02:29
		Re: Operator precedence By: Christoph Michael Bec on Tue, 25 February 2014 18:41
		Re: Operator precedence By: Thomas 'PointedEars' on Tue, 25 February 2014 18:55
		Re: Operator precedence By: Christoph Michael Bec on Tue, 25 February 2014 20:36
		Re: Operator precedence By: Ben Bacarisse on Tue, 25 February 2014 03:08
		Re: Operator precedence By: Thomas 'PointedEars' on Tue, 25 February 2014 03:17
		Re: Operator precedence By: Ben Bacarisse on Tue, 25 February 2014 04:45
		Re: Operator precedence By: GS on Tue, 25 February 2014 21:45
		Re: Operator precedence By: Jerry Stuckle on Mon, 24 February 2014 12:00
		Re: Operator precedence By: Christoph Michael Bec on Mon, 24 February 2014 17:11
		Re: Operator precedence By: Jerry Stuckle on Mon, 24 February 2014 19:27
		Re: Operator precedence By: Christoph Michael Bec on Tue, 25 February 2014 00:25
		Re: Operator precedence By: Jerry Stuckle on Tue, 25 February 2014 01:40
		Re: Operator precedence By: Ben Bacarisse on Mon, 24 February 2014 21:23
		Re: Operator precedence By: Jerry Stuckle on Mon, 24 February 2014 21:45
		Re: Operator precedence By: Ben Bacarisse on Tue, 25 February 2014 04:32
		Re: Operator precedence By: Jerry Stuckle on Tue, 25 February 2014 04:47
		Re: Operator precedence By: Ben Bacarisse on Tue, 25 February 2014 16:56
		Re: Operator precedence By: Jerry Stuckle on Tue, 25 February 2014 18:59
		Re: Operator precedence By: Christoph Michael Bec on Tue, 25 February 2014 19:19
		Re: Operator precedence By: Thomas 'PointedEars' on Tue, 25 February 2014 19:43
		Re: Operator precedence By: Jerry Stuckle on Tue, 25 February 2014 21:02
		Re: Operator precedence By: Jerry Stuckle on Tue, 25 February 2014 21:01
		Object constructors/destructors (was: Operator precedence) By: Christoph Michael Bec on Tue, 25 February 2014 21:19
		Re: Object constructors/destructors By: Jerry Stuckle on Tue, 25 February 2014 21:32
		Re: Object constructors/destructors By: Christoph Michael Bec on Tue, 25 February 2014 21:55
		Re: Object constructors/destructors By: Jerry Stuckle on Tue, 25 February 2014 22:01
		Re: Object constructors/destructors By: Adam Harvey on Tue, 25 February 2014 23:22
		Re: Object constructors/destructors By: Jerry Stuckle on Wed, 26 February 2014 02:10
		Re: Object constructors/destructors By: Christoph Michael Bec on Wed, 26 February 2014 20:10
		Re: Object constructors/destructors By: Jerry Stuckle on Wed, 26 February 2014 21:01
		Re: Object constructors/destructors By: Christoph Michael Bec on Wed, 26 February 2014 21:59
		Re: Object constructors/destructors By: Jerry Stuckle on Wed, 26 February 2014 22:19
		Re: Object constructors/destructors By: Christoph Michael Bec on Wed, 26 February 2014 22:39
		Re: Object constructors/destructors By: Jerry Stuckle on Thu, 27 February 2014 03:30
		Re: Object constructors/destructors By: Christoph Michael Bec on Thu, 27 February 2014 17:28
		Re: Object constructors/destructors By: Jerry Stuckle on Thu, 27 February 2014 21:09
		Re: Object constructors/destructors By: Christoph Michael Bec on Fri, 28 February 2014 13:52
		Re: Object constructors/destructors By: Jerry Stuckle on Fri, 28 February 2014 14:08
		Re: Object constructors/destructors By: Christoph Michael Bec on Fri, 28 February 2014 15:52
		Re: Object constructors/destructors By: Jerry Stuckle on Fri, 28 February 2014 16:03
		Re: Object constructors/destructors By: Thomas 'PointedEars' on Thu, 27 February 2014 00:00
		Re: Object constructors/destructors By: Jerry Stuckle on Thu, 27 February 2014 03:39
		Re: Object constructors/destructors By: Thomas 'PointedEars' on Thu, 27 February 2014 17:29
		Re: Object constructors/destructors By: Jerry Stuckle on Thu, 27 February 2014 21:14
		Re: Object constructors/destructors By: Christoph Michael Bec on Tue, 25 February 2014 23:18
		Re: Object constructors/destructors By: Jerry Stuckle on Wed, 26 February 2014 02:08
		Re: Object constructors/destructors By: Richard Damon on Wed, 26 February 2014 12:50
		Re: Object constructors/destructors By: Jerry Stuckle on Wed, 26 February 2014 13:44
		Re: Object constructors/destructors By: Richard Damon on Thu, 27 February 2014 04:49
		Re: Object constructors/destructors By: Jerry Stuckle on Thu, 27 February 2014 13:25
		Re: Object constructors/destructors By: Richard Damon on Sat, 01 March 2014 17:56
		Re: Object constructors/destructors By: Jerry Stuckle on Sat, 01 March 2014 19:22
		Re: Object constructors/destructors By: Richard Damon on Sun, 02 March 2014 19:28
		Re: Object constructors/destructors By: Jerry Stuckle on Sun, 02 March 2014 20:42
		Re: Object constructors/destructors By: Richard Damon on Sun, 02 March 2014 22:14
		Re: Object constructors/destructors By: Jerry Stuckle on Sun, 02 March 2014 22:48
		Re: Object constructors/destructors By: Tim Streater on Sun, 02 March 2014 23:05
		Re: Operator precedence By: Ben Bacarisse on Tue, 25 February 2014 21:08
		Re: Operator precedence By: Christoph Michael Bec on Tue, 25 February 2014 21:29
		Re: Operator precedence By: Ben Bacarisse on Tue, 25 February 2014 23:15
		Re: Operator precedence By: Richard Damon on Tue, 25 February 2014 03:41
		Re: Operator precedence By: Jerry Stuckle on Tue, 25 February 2014 04:59
		Re: Operator precedence By: Richard Damon on Sat, 01 March 2014 18:39
		Re: Operator precedence By: Jerry Stuckle on Sat, 01 March 2014 19:29
		Re: Operator precedence By: Richard Damon on Sun, 02 March 2014 20:22
		Re: Operator precedence By: Jerry Stuckle on Sun, 02 March 2014 20:49
		Re: Operator precedence By: Christoph Michael Bec on Tue, 25 February 2014 18:15
		Re: Operator precedence By: Ben Bacarisse on Sun, 23 February 2014 20:56
		Re: Operator precedence By: Christoph Michael Bec on Mon, 24 February 2014 13:28

Previous Topic:	Correlating curl resources to some other object.
Next Topic:	Experienced Web designer required

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu May 09 20:50:13 GMT 2024

Total time taken to generate the page: 0.04696 seconds