On Wed, 29 Sep 1999, Aaron Scott-Boddendijk wrote:
> Allowing a compile to give feedback through the compiler for
> unfinished or untested code. It's possible the To-Do lists in D5 might
> fill enough of this wishes shoes.
Not quite, say I write a component that handles security
checking/functionality limiting for my app which is used in several other
apps by other programmers.
When property SecurityEnabled is false, no checks are performed, which is
good for inhouse testing, or testing-whilst-coding, but you don't want to
compile you're end product without security. Simple things like that that
the user (end-user developer) might not be aware of.
Or, the other case, I have 2-3 components that need to be linked to other
components in the project before they work properly (much like a dbedit
goes to a dataset, my unitedit goes to a unitsystem comp. I'd like to
fire a warning if UnitEdit1.UnitSystem = '', it may be that the property
gets set in code. For other things, that are likely to crash the app, I'd
like to maybe generate an error and stop the compile.
Mark
--
Mark Derricutt | Chalice of Blood
Software Developer | New Zealand Christian Music News
Auckland, New Zealand | http://www.chalice.gen.nz
[EMAIL PROTECTED] | UIN: 1934853
Getting jiggy with Days of the New - Days of the New
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
