qoy (i do not have that many points :-)

Could a private constructor be useful for a Delphi object? Describe a constallation.
What is the problem of Delphi 5 (maybe also 4 and 6) with a private constructor?

100 points for an answer to both parts. 50 for one part.
No sample code required. A good explanation is enough.
Maybe more points for a good description.
LVL 11
robert_marquardtAsked:
Who is Participating?
 
geobulConnect With a Mentor Commented:
Hi,
Nice question, Robert.

I've never used it before but made some tests. And the tests show that:
1. if the object is created in the same unit then the private constructor is executed.
2. if the object is created outside its unit then the inherited constructor is used instead.

So, the conclusion:
A private constructor could be useful for an object which is used by another object in the same unit to perform some special operations (initialization) which are specific to that second (master) object and are not mandatory when the first object is used by itself.

Is that clear enough (understandable)? Does that make sense?

Regards, Geo
0
 
kretzschmarCommented:
qoy->question of the year?

never used a private constructor,
no idea whats thebenefit of of ths

listening . . .

meikl ;-)
0
 
robert_marquardtAuthor Commented:
To precise the question: ONLY a private constructor!
Yes, it IS useful.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
geobulCommented:
About your second question: I can't find out any problems using private constructors in Delphi 5. What did you have in mind?
0
 
robert_marquardtAuthor Commented:
geobul, almost there.
1. not bad, but i have a more useful task implemented already
2. you mentioned the problem, but failed to recognize it.
0
 
robert_marquardtAuthor Commented:
I will solve the question tomorrow.
0
 
kretzschmarCommented:
yep, do it :-)
0
 
robert_marquardtAuthor Commented:
I use a private constructor as geobul mentioned. A controller object (component) creates them. The objects itself represent USB devices. No user interference is needed because the devices are plugged and as reaction a device object is created. A user/program created object is not advisable here because a 1 : 1 representation is always needed. For that i wanted to make it impossible to create a device object.

The problem is mentioned by geobul as 2. The TObject.Create is not hidden because it is a static method not a virtual method.
This i consider as a language problem. Visibility clashes with inheritance.
Locally the private constructor hides the TObject.Create. Externally TObject.Create is still visible.
I also get no visibility warning like for virtual methods. So the most difficult to understand language part is completely unvocered by hints or warnings.

I will award geobul the 100 points. Maybe more. It was a really tricky question.
0
 
kretzschmarCommented:
aplause ;-)
0
 
geobulCommented:
Wow, so many many thanks, Robert :-)))

I see what you had in mind now. On the one hand that is some kind of flexibility but on the other hand the lack of warning messages is really bad. This may lead to very-hard-to-find errors.

Thank you again and best regards, Geo
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.