Graeme Geldenhuys <>:

> A very quick and dirty solution would be to reimplement the public
> Create() constructor and immediately raise an exception inside it,
> explaining the problem. That way if any developer tries to use that
> default constructor, they will get an error - instead of some silent
> side-effect later on. Then implement a new public custom constructor
> with your desired code.

Why "public" then? Perhaps I don't *want* the user to create instances of this 
class in an uncontrolled way?

Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher!
fpc-pascal maillist  -

Reply via email to