🚀 go-pugleaf

Thanks Randy,
 I've been using BCB for a few years now, but have just learnt what the term
inheritance means,
I thought it was something like that, but wasn't clear. At least one reader
has benefited!
Though one question you may be able to tell me I understand classes are
objects, but am I using correct terminology if I call a structure an object.
What other kinds of Objects are besides classes, or is it all classes.
Digby Millikan
Geolite Mining Systems
digby@geolite.one.net.au

"Digby Millikan" <digbym@one.net.au> wrote in message
news:3b0db8b0$1_2@dnews...

> Though one question you may be able to tell me I understand classes are
> objects, but am I using correct terminology if I call a structure an
object.
> What other kinds of Objects are besides classes, or is it all classes.

Digby

See if this helps to clear up some terminology...

A Class is like a cookie cutter; it is the pattern from which you cut out
cookies (Objects).

You design a Class by defining what properties and methods you want to see
in each of the Objects you will create from that Class.

An Object is a particular instance of a Class, e.g. 'Joe Bloggs' is an
object of the class TPerson, 'ABC Mining' is an instance of the class
Company, etc.

A Structure is not an Object, but more correctly an Object is a Structure,
in that it is essentially a record that can contain methods as well as
properties.

You can also use a Class without an Object, if you declare Class Variables
or Class Methods; these provide what is called Singleton behaviour, in that
they act on the one single 'cookie cutter' rather than each individual
'cookie'.

Hope this helps a bit.

--
Joanna Carter
Remove .Hat to reply

>You can also use a Class without an Object, if you declare Class Variables
>or Class Methods;

Are these the same as "class statics"?

Greetings,
Julio

Randy,

Thanks for the link. If you are ever looking for something more to write
about on this topic, may I suggest that you consider a discussion of "best
practices"? Of even a list of DOs and DON'Ts. I happen to manage a number of
Delphi programmers and quite often, while they know what OOP is, they very
often have a problem coming up with a OO design for a project. (Or at lease
I think they have a problem coming up with a good design! <g>).

Karl


"Randy Charles Morin" <rmorin@kbcafe.com> wrote in message
news:3b021472$1_1@dnews...
> I'm looking for feedback on an article I wrote on OOP Concepts. The
article
> is at the following URL.
> http://www.kbcafe.com/articles/oop.concepts.html
> Thanks you very much for your time and sorry for the intrusion.
> --
> Randy Charles Morin
> http://www.kbcafe.com/randycharlesmorin
>
>
>
>

Yes.

A static variable or method is normally referred to as a class method or
class variable.

Hope that helps,

Brent

Karl,

> [...] I happen to manage a number of
> Delphi programmers and quite often, while they know what OOP is, they very
> often have a problem coming up with a OO design for a project.

The reason simply being that object oriented programming and
object oriented design are two totally different skills. (You wouldn't
expect a bricklayer to do the job of an architect, would you?)

CU
Elmar.