).
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: Wilfried Mestdagh [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Wednesday, December 28, 2005 9:17 PM
Subject: Re: [twsocket] ICS-V6 files and classes naming
Hello Francois,
I wonder if I should
I wonder if I should also change all class names. For example rename
TWSocket to TOverbyteIcsSocket or TIcsSocket. This way, ICS component
would be clearly identified. This of course would require a lot of
changes in
existing applications, including in dfm.
I'm not fully against, I say
I'm still wondering.
Renaming everything and cleaning up thing is of course very interesting
for
new users. But for existing users, it would require a lot of work
converting
their old code to the new versions. And that may be fatal to ICS: current
user would not upgrade to new version
Francois PIETTE a écrit :
That seems to be nicer. But for those who are still working with old
compilers, that wouldn't do it.
Except if you make the old versions available (leaving a place where to
download the V5).
I don't plan to delete V5 ! It will stay there for download.
i didn't mean
I have not taken the final decision yet.
I'm still grabbing other's opinion.
Rename classes as wanted ie. TWSocket to TIcsSocket (or using any other
prefix), then create proxy unit like below.
a) It would have some sort of redirection from old types to new types:
unit IcsProxyV5;
type
Hello,
Excellent idea so you can use either TWSocket or TIcsSocket as you
want !
Rename classes as wanted ie. TWSocket to TIcsSocket (or using
any other prefix), then create proxy unit like below.
type
TWSocket = class(TIcsSocket);
FP What a good idea ! I wonder how I didn't had it
All in all I wonder if it is not better to simply make V6 as
compatible as possible with V5. That is dropping support for
old compilers (this would make the source code much cleaner)
and adding new features without breaking existing ones. If I
do that, current ICS user would have no
I do not agree with you. I can't say it never happened, but it was
very uncommon that any change in ICS required _application_ code
change.
The most recent example is SSL, the versions in the last few months
required numerous application changes over the original implementation,
it's all
I renamed ICS-V6 files to have ICS files clearly identified. The consequence
is that all source code using the component must be updated to change file
names in their uses clause.
I wonder if I should also change all class names. For example rename
TWSocket to TOverbyteIcsSocket or TIcsSocket.
- Original Message -
From: Francois PIETTE [EMAIL PROTECTED]
To: twsocket@elists.org
Sent: Wednesday, December 28, 2005 4:20 PM
Subject: [twsocket] ICS-V6 files and classes naming
...
I wonder if I should also change all class names. For example rename
TWSocket to TOverbyteIcsSocket
Hello,
I tried to Install both packages but there are some problems like
THttpClient class already exists.
Keeping both may be usefull to be able to open old V5 applications and
also new V6 ones.
FT Maybe I missed: why do you need to rename? Why would one person need to
FT install both v5 and
Maybe I missed: why do you need to rename?
I said: This way, ICS component would be clearly identified.
The idea is really to have better naming convention. To start on better
basis.
My idea is to release V6 for the 10th ICS birthday which is in april 2006.
This release would break the main
I tried to Install both packages but there are some problems like
THttpClient class already exists.
Keeping both may be usefull to be able to open old V5 applications and
also new V6 ones.
You can simply select/unselect the packages from hte component/install
packages menu. Just a little
TWSocketV6 sounds good for example so in the future you will be able
to have TWSocketV7, TWSocketV8 ...
OK so TWSocketICS ?
Not better. A component name need a prefix, not a suffix.
TIcsSocket or TIcsWSocket or TOverbyteIcsSocket or...
--
[EMAIL PROTECTED]
http://www.overbyte.be
--
To
Hello Francois,
I wonder if I should also change all class names. For example rename
TWSocket to TOverbyteIcsSocket or TIcsSocket. This way, ICS component would
be clearly identified.
True.
This of course would require a lot of changes in
existing applications, including in dfm.
No the
Scrive Francois PIETTE [EMAIL PROTECTED]:
I renamed ICS-V6 files to have ICS files clearly identified. The consequence
is that all source code using the component must be updated to change file
names in their uses clause.
This will not a big problem when it generate an error at compile
16 matches
Mail list logo
