[fpc-devel] possible 'dynlibs' unit issue

[Daniël Mantione]

Op Tue, 19 Jan 2010, schreef Dariusz Mazur:

> Is this possible to forbid this at compile time?

An easy solution is to wrap it inside a record. This is good practise as 
it prevents accidental bugs like accidentally writing parameters in the 
wrong order when calling a procedure. It's basically the point of type 
safety.

Some languages have "opaque" types designed for this purpose, the 
difference being that a record only protects against accidental 
calculations (you could modify the field in the record), while an actual 
opaque type could enforce it.

Daniël