Re: The trend is to move away from Delphi...


"Andre Kaufmann" <andre.kaufmann_remove_@xxxxxxxxxxx> wrote in message

DinkumWare. Even the linker could use some love (although it
did get a big update when BDS 2006 came out so it doesn't
barf on big projects).

I would be very happy if I could agree on your statement about the
linker not barfing on big projects. But I still cannot compile our
largest project anymore due to this ..... linker problem.

Linker problems still exist!??

That's one of the reasons why I left Borland!!!!

Seriously, if Borland can give these basic QA issues out the way regardless
it only effects a few people, then there is ABSOLUTELY nothing they can do
that will change the lost of developers.

If Borland wants to take a "step back into the balcony" and begin to
reintroduce some original highly successful product line packaging, which
has caught my eye again, they need to also get a renewed commitment to old
QA corporate and customer support mantras:

"Getting it right.... the first time."
"The customer is always right."

Its the attitude folks!!!

If they can't fix your linker problem, that should go along way in telling
you how much they really care in supporting its developer's market across
the board. Come on, a Linker Problem? What at best? 1/2 day work for 1
person to fix it?

Serious, this is ridiculous to hear this.

The last time, it was the command line linker using the API function
GetFileInformatonByHandle() which failed when linking in resources that were
stored across the network on Win95 machines. They BLAMES me for using
Win95, when in fact MSDN says:

Remarks

Depending on the underlying network components of the operating
system and the type of server connected to, the
GetFileInformationByHandle function may fail, return
partial information, or full information for the given file.
In general, you should not use GetFileInformationByHandle unless
your application is intended to be run on a limited set of
operating system configurations

So the linker should had not used this function to support all Windows OS
and also any remote NON-WINDOWS storage device that might have problems.

Borland refusing to fix this simple problem, especially after I was promised
in direct email that it will be fixed, and then watching updates and patches
come without the fix, was the straw that broke the camel back for me.

This "Don't Care" QA mentality what they got to FIX first before they can
even try any new "Turbo" marketing!!

--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com







.

Relevant Pages

  • Re: The trend is to move away from Delphi...
    ... linker not barfing on big projects. ... If they can't fix your linker problem, that should go along way in telling ... So support got much better than in the past, though that doesn't help me anyways. ... So we can choose the best product on the market to compile our projects. ...
    (borland.public.delphi.non-technical)
  • Re: SAS/C error?
    ... >> As for the linker problem, I think I may caused it myself. ... > necessarely optimal precision (the ieee lib code is smarter in this ...
    (comp.sys.amiga.programmer)
  • Re: SAS/C error?
    ... As for the linker problem, I think I may caused it myself. ... necessarely optimal precision (the ieee lib code is smarter in this ...
    (comp.sys.amiga.programmer)
  • Re: The trend is to move away from Delphi...
    ... Even the linker could use some love. ... linker problem. ... And I>> hope << seriously that DevCo will add either support of generating a PDB compatible debug format creation to both - Delphi and BCB - or debugging of dump files in BDS itself. ...
    (borland.public.delphi.non-technical)
  • patch needed (112963-22)
    ... It's for Solaris 9. ... patch fixed a security vulnerability in the linker. ... To fix this problem, I ...
    (SunManagers)