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 #185085 is a reply to message #185084]

Tue, 25 February 2014 22:01

Jerry Stuckle
Messages: 2598
Registered: September 2010

Karma:

Senior Member

On 2/25/2014 4:55 PM, Christoph Michael Becker wrote:
> Jerry Stuckle wrote:
>
>> On 2/25/2014 4:19 PM, Christoph Michael Becker wrote:
>>> Jerry Stuckle wrote:
>>>
>>>> On 2/25/2014 2:19 PM, Christoph Michael Becker wrote:
>>>> > Jerry Stuckle wrote:
>>>> >
>>>> >> I have my own problems with PHP - for instance, it is entirely
>>>> >> possible
>>>> >> to create an object without calling a constructor - a violation of OO
>>>> >> principles. But I work around it.
>>>> >
>>>> > How is it possible to create an object without its constructor (if
>>>> > defined) being called?
>>>> >
>>>>
>>>> Load the object from the $_SESSION. The constructor will not be called.
>>>>
>>>> However, the constructor is called when the original object was created,
>>>> and the destructor called when the original object goes out of scope.
>>>> The destructor is also called when the object loaded from the $_SESSION
>>>> goes out of scope.
>>>>
>>>> The result is one constructor call and two destructor calls. A
>>>> violation of OO principles.
>>>
>>> Um, I'm not sure whether this is a violation of OOP principles. Storing
>>> an object in the session requires serialization of the object, what is
>>> somewhat comparable to cloning an object. So actually, you're not
>>> working with the *same* object.
>>>
>>> Anyway, you can work around these issues by using the magic methods
>>> __sleep() and __wakeup(), as you probably know. :)
>>>
>>
>> Yes, it is a violation. When the script starts, the object is
>> serialized in the $_SESSION. But it does not exist in the script.
>> Creating it requires a constructor call.
>
> It requires the object to be created in memory somehow, but the defined
> constructor function is not called in this case.
>

Which is a violation of OO principles.

>> OO principles require exactly
>> one constructor call and one destructor call for every object created.
>> Note these may be explicit or implicit, and the functions may be noops,
>> but the calls must still be made.
>
> When you're cloning an object, its constructor will not be called either.
>

It is in every other language. For instance, in Java, clone() acts like
a copy constructor. C++ doesn't have a clone() method, but it does have
a copy constructor.

>> That is not the case here; you get
>> one constructor call and two destructor calls.
>
> I firmly believe that it wouldn't make sense to call a (user-defined)
> constructor when unserializing or cloning an object. A constructor
> usually serves to initialize an object -- what already had happened in
> both cases.
>

It makes perfect sense. Not everything is necessarily valid in the new
object. For instance, a logging object may require opening the log
file. There are many instances where a resource is no longer available
and needs to be recreated.

PHP's method is only a shallow copy. Copy constructors and the like
were created when a deep copy is required (quite often in other languages).

>> I know of no other OO language which would allow this.
>
> Others may.
>

None that I know of. Please name one.

--
==================
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: Fri May 10 09:21:53 GMT 2024

Total time taken to generate the page: 0.05946 seconds