In addition to Rob's suggestion, a unit containing
only declarations of types, constants and records and
no implementation section is helphful, especially when
sharing these amongst multiple projects. This is the
equivalent of a C/C++ .h file. For example, I've
created a Control Panel applet, Windows Service and
console application that share the same unit for
constants. With no implementation, it never needs to
use another unit in your project (though it might
require Windows, Classes, SysUtils or other unit in
the Uses clause to access their constants); this
avoids the rare circular reference (much more a
liability of large C/C++ propjects than Delphi).
Bart
> Date: Sun, 16 Apr 2006 20:24:33 -0500
> From: Rob Kennedy <[EMAIL PROTECTED]>
>Subject: Re: Re: Passing enumerated types as
parameters
>kenhaile wrote:
> Thanks for the reply Rob. Yes, the problem is
because I've delcared
> them twice. Is there any equivalent to the "C"
header file for
> Delphi? I'm not sure where such a declaration could
be placed.
>Place the declaration in the interface section of
whatever unit you
>want. Include that unit on the "uses" clause of any
other unit that
>needs access to that declaration.
>You can read more about how units work in the help
file.
>Rob
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-----------------------------------------------------
Home page: http://groups.yahoo.com/group/delphi-en/
To unsubscribe: [EMAIL PROTECTED]
YAHOO! GROUPS LINKS
- Visit your group "delphi-en" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
