Is there a way I can turn this warning of? It is irritating me. Is shown
292 times, for every IncludeTrailingBackslash. Slows down compilation by
20%. I hate it.
Kind regards and thanks for any tips
Alexander
Jeeez!
And what should we use in Kylix instead?
PS: i'm still happy with D5. And couldn't think that
??cludeTrailingBackslash function would not be available in Kylix. Smth very
strange occured :(
Use
{$ifdef VER140} // Delphi 6
{$WARN SYMBOL_PLATFORM OFF}
{$endif}
Cheers
-- Jan
[posted and mailed]
"Alexander" <TheS...@etc.be> wrote in news:3d33cced_2@dnews:
May god be with us.
Kind regards and thanks for the tips
IncludeTrailingPathDelimiter ???
This function is there on D6 and Kylix.
Saves you a lot of trouble
Rory
"Alexander" <TheS...@etc.be> wrote in message news:3d33deee_1@dnews...
>> IncludeTrailingPathDelimiter ???
Ever worked in a real environment (no offence, retorical question)? :-) One
just doesn't change it's source with every patch to the compiler. I don't
feel like modifying all code :-(
If the compiler is compiling on Windows OS for a Windows OS, it should *NOT*
nag about this, by default. imho. Why mention to me that this function is
not available in linux. Who wants to know that anyway, I'm compiling on
Windows for Windows, so incompatibility with Linux is the least of my
concerns? (This doesn't mean that at home, in my free time I wouldn't try
to compile for Linux)
We already went thru enough shit with their proxies, variants, ... I have
to check everytime over 2.000.000 lines of code, takes me several weeks of
extreem boring work, makes me pissed of, like reïnventing the wheel.
Kind regards
Alexander
> > Today we are upgrading are entire R&D to Windows XP, Delphi 6 and Visual
> > SourceSafe. Yesterday it all was Win2K, D5 and FreeVCS.
D6 is still reported to have bugs.
WinXP is not that stable as w2k imho. And it needs more RAM by default?
Why could You need such an upgrade? Quest for glory?
PS: is it upgradem or now You have unused disks of D5 and w2k?
> > May god be with us.
Wish you luck!!!
> It was a very important thing to rename this function...
Is this serious? Why didn't they just do
function IncludeTrailingBackslash() : string
begin
Result := IncludeTrailingPathDelimite(Str);
end;
This would not require a new directive? Does it? Put it in the help file
that it is there for compatibility and let it rest. And for those nagging
about speed loss, implement the function twice. And for those nagging about
exe growing in size due to this extra implementation, doesn't the linker
remove whatever there is not to be linked?
Somethimes I wonder if Delphi R&D ever bother about backwards compatibility.
And with that I don't mean go from D6 to D5, but make it easy to go from D5
to D6. D2 - D3 ==> Pain in the ass. D3 - D4 ==> Dito. D4 - D5 (actually
only a bugfix of a very instable version ;-)) D5 - D6 a compleet disaster.
> They'd be better to fix D6bugs which a still discussed in these ng's.
Hmm, are they though? And is there a list?
> Quest for glory?
I was compiling on a PIII, 333 with 128 MB. It took me up to 7 min to do a
build. Now it is 1.6 min. (And I like the fluffy interface of XP). Now I
have a brand new PC (PIV 2.2, 512RIMM ;-)).
Kind regards
Alexander
I must say, I don't understand what the fuss is about.
You've been upgrading you MicroShit platform, but not the development
environment you use.
That's a bit double now isn't it.
At my company, we have a large project built in D5.
It was converted to D6 in a matter of minutes.
I'm always pushing to the latest possible 'stable' release.
If it's in the store, stability is a fact. Sure there will be bugs.... (ever
met software that hasn't got any???), but that's not hte issue now is it.
Yep, I got my company to upgrade all D5 licenses to D6, without as much as a
remark from my users...(I still wonder if they even noticed)
It has always been:
Upgrade, and NEVER look back :)
Laterz,
Rory
Lucky basterd ;-)
> I'm always pushing to the latest possible 'stable' release.
I agree
> Upgrade, and NEVER look back :)
I agree if you change the phrase to Upgrade, never look back and pray your
ass off ;-)
Kind regards
Alexander
LOL
Great d;-D
Rory
>
> Kind regards
>
> Alexander
>
>
>
Use non-platform-specific calls, such as IncludeTrailingPathDelimiter
--
Dave Nottage (TeamB)
Best thing about Visual SourceSafe is VSS Connexion
(http://www.epocalipse.com) - it changes the way you use your
versioning system, being able to check thing in/out like that.
We bought that one, I'm very satisfied with it.
Kind regards
Alexander
"Thomas Christensen" <t...@nospam.dk> wrote in message
news:3D343BC0...@nospam.dk...
Hi,
> Ever worked in a real environment (no offence, retorical question)? :-) One
> just doesn't change it's source with every patch to the compiler. I don't
> feel like modifying all code :-(
Well the move from D5 to D6 compiler is not just a patch, it is a
complete new compiler versions.
You would only move your project to a new compiler version if the
benefits outweighed the costs.
I still have active projects in all versions of Delphi since D2, that
have not be 'ported' to a later compiler because I did not need the new
features that the newer compiler offered, or I wanted a new feature, but
could not justify the effort of porting.
> We already went thru enough shit with their proxies, variants, ... I have
> to check everytime over 2.000.000 lines of code, takes me several weeks of
> extreem boring work, makes me pissed of, like reïnventing the wheel.
But you obviously did the port for a reason, so that server weeks of
porting was worth it?
J