Regarding Contructors
-
Hi guys, Is a Constructor only accessible by the members of a function in a particular class? Suppose, I have a class where I've two functions. If I declare a constructor in one of the functions, wont it be accessible by the other one? Somebody please explain it to me. I am greatly confused!:suss: Your help will be truly appreciated, Rajdeep.NET
-
Hi guys, Is a Constructor only accessible by the members of a function in a particular class? Suppose, I have a class where I've two functions. If I declare a constructor in one of the functions, wont it be accessible by the other one? Somebody please explain it to me. I am greatly confused!:suss: Your help will be truly appreciated, Rajdeep.NET
-
stancrm wrote:
You can declare constructor in a Class, not in Function.
Hi Stancrm, so, if I declare a constructor in a class, will it be accessible by all the functions present in the that class? Is it also accessible by other classes? :^)
-
stancrm wrote:
You can declare constructor in a Class, not in Function.
Hi Stancrm, so, if I declare a constructor in a class, will it be accessible by all the functions present in the that class? Is it also accessible by other classes? :^)
Hi, I am not sure what is the question is ... constructors can be declared to create a new object of that class ... they can by public (accessible to outer classes) or private (only to the same class) now its not commonly used to declare a private constructor ... most common case is when you are creating a singleton object (read about singleton design pattern)... but can we use constructors in the same class ? Yes we can ... no roles can forbid doing so ...
Sincerely Samer Abu Rabie Imagination is more important than knowledge !
-
Hi guys, Is a Constructor only accessible by the members of a function in a particular class? Suppose, I have a class where I've two functions. If I declare a constructor in one of the functions, wont it be accessible by the other one? Somebody please explain it to me. I am greatly confused!:suss: Your help will be truly appreciated, Rajdeep.NET
Look, you've been posting basic questions all over this forum. Here's an idea - rather than running against a problem, posting it here on CP and then potentially waiting hours for somebody to reply; why not actually go out and buy a book that covers the basics? Then everytime you run up against something you don't know the answer to, you've got two choices; 1. read the book; 2. whack yourself around the head with the book until the urge to post a basic question is gone.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
stancrm wrote:
You can declare constructor in a Class, not in Function.
Hi Stancrm, so, if I declare a constructor in a class, will it be accessible by all the functions present in the that class? Is it also accessible by other classes? :^)
Just what use do you suppose a constructor would be if you couldn't access it from outside the class? Go read a book on C# and/or programming.
No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced. This message is made of fully recyclable Zeros and Ones
-
Just what use do you suppose a constructor would be if you couldn't access it from outside the class? Go read a book on C# and/or programming.
No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced. This message is made of fully recyclable Zeros and Ones
In a Factory pattern, you would hide constructors by making them protected or private, then provide a public CreateSomeObject() method that actually invokes the appropriate constructor. :)
Luc Pattyn [Forum Guidelines] [My Articles]
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Show formatted code inside PRE tags, and give clear symptoms when describing a problem.
-
Look, you've been posting basic questions all over this forum. Here's an idea - rather than running against a problem, posting it here on CP and then potentially waiting hours for somebody to reply; why not actually go out and buy a book that covers the basics? Then everytime you run up against something you don't know the answer to, you've got two choices; 1. read the book; 2. whack yourself around the head with the book until the urge to post a basic question is gone.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Has been suggested many times already, to no avail. Also good replies don't sink in. I stopped reading his posts. And his replies to other posts. :)
Luc Pattyn [Forum Guidelines] [My Articles]
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Show formatted code inside PRE tags, and give clear symptoms when describing a problem.
-
Just what use do you suppose a constructor would be if you couldn't access it from outside the class? Go read a book on C# and/or programming.
No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced. This message is made of fully recyclable Zeros and Ones
There are plenty of reasons for keeping a constructor private within a class, you just need to know why. Examples - 0. Singleton or cached class where you want to control the instatiation through a static method. The method is public, the constructor private. 1. You have several public constructors and wish to use one combined super constructor that talkes EVERY parameter, however you don't want to make the super constructor available - again you keep it private.
Panic, Chaos, Destruction. My work here is done.
-
Has been suggested many times already, to no avail. Also good replies don't sink in. I stopped reading his posts. And his replies to other posts. :)
Luc Pattyn [Forum Guidelines] [My Articles]
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Show formatted code inside PRE tags, and give clear symptoms when describing a problem.
