PLEASE Define Non Breaking
Nathanial Woolls
CodeGear Delphi for Microsoft Windows
---------------------------
Cannot load package 'vclie100.' It contains unit 'UrlHist,'which is
also contained in package 'vcliex100'
---------------------------
OK
---------------------------
---------------------------
bds.exe - Entry Point Not Found
---------------------------
The procedure entry point @$xp$15Idglobal@TBytes could not be located in
the dynamic link library IndySystem100.bpl.
---------------------------
OK
---------------------------
Marco Caspers
Dunno about the vclie one, but for the Indy ones we where told to
expect it.
And a recompile fixes it.
--
Nathanial Woolls
> Dunno about the vclie one, but for the Indy ones we where told to
> expect it.
> And a recompile fixes it.
Where were we told to expect it? The only announcement about update 3
I've seen on these newsgroups was Nick's post:
"So, who is the first one to get Update 3?
-- Nick Hodges Delphi Product Manager - CodeGear
http://blogs.codegear.com/nickhodges"
I read through the information here:
http://dn.codegear.com/article/36858
and also didn't see anything about this. Furthermore, what about those
who do the automatic upgrades? I've not seen any warnings or messages
shown by those.
If this was stated beforehand, that makes it about || that much more
okay. If Codegear is going to break binary compatibility in these "non
breaking" releases, then change the file names and versions. Call the
files XXX110.BPL. If they are going to keep it 100.BPL, and keep the
VER, then they are screwing customers that have 3rd party components
built against these.
When Delphi 2008 comes out (for instance), customers will either wait
for their 3rd party vendors to support it, or they will try compiling
themselves. However, almost every update to D2007, and D2007 itself
(which was "non breaking") "broke" 3rd party components.
Why was this "non breaking" stuff even done?
Bruno Fierens [tmssoftware.com]
also bitten by this
sad...
Marco Caspers
<snip>
> and also didn't see anything about this. Furthermore, what about
> those who do the automatic upgrades? I've not seen any warnings or
> messages shown by those.
From the release notes you quoted:
Unit interface compatibility
For the most part, the product maintains unit interface compatibility
with BDS2006. However, the dbExpress VCL breaks this compatibility in
three units: SQLExpr, DBXpress, and SQLConst.
So at least this part is explicitly mentioned as causing breakage.
> If this was stated beforehand, that makes it about || that much more
> okay.
I guess you mean that it isn't ok.
I agree, if you tell it isn't breaking it shouldn't be breaking.
<snip>
> When Delphi 2008 comes out (for instance), customers will either wait
> for their 3rd party vendors to support it, or they will try compiling
> themselves. However, almost every update to D2007, and D2007 itself
> (which was "non breaking") "broke" 3rd party components.
True, if you didn't have the source code you'd be the fish in the
frying pan.. Fortunately for Indy at least you got all the source code.
> Why was this "non breaking" stuff even done?
Your guess is as good as mine.
I think it just "looked good", and i suppose that for some customers it
holds true, just for an unfortunate group it won't be.
--
Sebastian Ledesma [Solidyne Labs]
that D2007 will be a non-breaking release,
but Highlander will be a breaking one, just read the
blogs/info/news/etc.etc.etc
Saludos
Sebastian
"Nathanial Woolls" <nwo...@nospam.gmail.com> escribió en el mensaje
news:46e7d41f$1...@newsgroups.borland.com...
Markus.Humm
> Was stated, several months ago,
> that D2007 will be a non-breaking release,
> but Highlander will be a breaking one, just read the
> blogs/info/news/etc.etc.etc
>
Yes but later they changed their mind to make Highlander
non-breaking for Win32 as well, even if Nick was against this
as it prevented some bug fixes/improvements from being done
for Win32. I don't have the source for this info unfortunatelly.
Greetings
Markus
nix
Have you found any fix for this (vclie100/vcliex100 issue). I fear i may
have to do something radical to get Delphi working again :-(
n
"Nathanial Woolls" <nwo...@nospam.gmail.com> wrote in message
news:46e7d41f$1...@newsgroups.borland.com...
Nathanial Woolls
> Was stated, several months ago,
> that D2007 will be a non-breaking release,
> but Highlander will be a breaking one, just read the
> blogs/info/news/etc.etc.etc
This is not true. Highlander, along with Update 3, were to be non-breaking.
Jeff Overcash (TeamB)
Non breaking for Win32, breaking for .NET.
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
And so I patrol in the valley of the shadow of the tricolor
I must fear evil. For I am but mortal and mortals can only die.
Asking questions, pleading answers from the nameless
faceless watchers that stalk the carpeted corridors of Whitehall.
(Fish)
Mike Orriss
> > This is not true. Highlander, along with Update 3, were to be
> > non-breaking.
>
> Non breaking for Win32, breaking for .NET.
Unfortunately, the point is irrelevant because Update 2 and 3 both
broke Win32.
--
Mike
Q Correll
| Unfortunately, the point is irrelevant because Update 2 and 3 both
| broke Win32.
As did the initial D2007 release. <g> "Non-breaking" is a boolean.
It's sort of like being pregnant... there's no in-between. <g>
--
Q
09/18/2007 09:30:01
XanaNews Version 1.17.5.7 [Q's salutation mod]