[delphizip] Re: Type name conflicts
- From: "James Turner" <james.d.h.turner@xxxxxxxxxxxx>
- To: <delphizip@xxxxxxxxxxxxx>
- Date: Mon, 27 Sep 2004 00:15:15 +0100
I thought about this ages ago.
My own thoughts were to use type names beginning TZM and enumerations
beginning zmx where x depended on the enumeration type.
To maintain backward compatibility, you could create a unit called, say,
zmCompat that contained constant definitions between the old enumeration
values and the new.
e.g.
unit zmCompat;
interface uses .........;
const
NewFile = zmpNewFile;
ProgressUpdate = zmpUpdate;
............ etc.
The same could be done with types.
Simply by including this extra unit in the uses list, old code could be made
to run without difficulty.
-- James Turner
----- Original Message -----
From: "R. Peters" <russellpeters@xxxxxxxxxxx>
To: <delphizip@xxxxxxxxxxxxx>
Sent: Sunday, September 26, 2004 10:49 PM
Subject: [delphizip] Type name conflicts
>I think the has about come when the type names and enumerations must be
> changed to reduce conflicts.
> Unless someone can come up with better idea I propose
> 1. Type names start with 'TZip'
> 2. enumerations start with 'z'
>
> Eg
> ProgressType = (NewFile, ProgressUpdate, ...
> TZipProgressType = (zptNewFile, zptProgressUpdate, ...
>
> It may be possible to reduce the impact of these changes via a define (in
> ZipConfig.inc) and some conditional statements but I doubt if that will
> stop
> all errors.
>
> It is a pity there is no way to tell Delphi that 2 enums are equivalent!
>
> - Russell Peters
>
> -----------
> To unsubscribe from this list, send an empty e-mail
> message to:
> delphizip-request@xxxxxxxxxxxxx
> and put the word unsubscribe in the subject.
>
-----------
To unsubscribe from this list, send an empty e-mail
message to:
delphizip-request@xxxxxxxxxxxxx
and put the word unsubscribe in the subject.
Other related posts:
