Re: Protecting against type mismatch errors
- From: "Howard Kaikow" <kaikow@xxxxxxxxxxxxx>
- Date: Sun, 26 Jun 2005 06:20:25 -0400
"Armin Zingler" <az.nospam@xxxxxxxxxx> wrote in message
news:Ol$wGMZeFHA.4040@xxxxxxxxxxxxxxxxxxxxxxx
> I think, resolving the problem at compile time helps to avoid runtime
> errors. That's why I mainly referred to strict typing.
Yes, but the code would be in a DLL and the class would be called from Word
VBA, so there's no possibility of controlling the calling code. When Office
is fully .NET-ized, maybe this will change.
In the case in question, I am making it (nearly) impossible to use the DLL,
other than by calling it from a Word template that I am supplying.
Even tho the VBA project in that template will be password protected, which
really is not secure anyway, I want to protect the DLL from somebody passing
in incorrect types.
.
- References:
- Protecting against type mismatch errors
- From: Howard Kaikow
- Re: Protecting against type mismatch errors
- From: Armin Zingler
- Re: Protecting against type mismatch errors
- From: Howard Kaikow
- Re: Protecting against type mismatch errors
- From: Armin Zingler
- Protecting against type mismatch errors
- Prev by Date: Re: Update Element in ArrayList Structure
- Next by Date: Re: VS Editor... The thin grey line that goes across the window
- Previous by thread: Re: Protecting against type mismatch errors
- Next by thread: Information on command line arguments and more fun stuff.
- Index(es):
Relevant Pages
|