Subject | Re: [ib-support] Best lanquage |
---|---|
Author | Paul Schmidt |
Post date | 2001-11-16T15:55:52Z |
On 15 Nov 2001, at 13:34, AdPay-Systech wrote:
www.sourceforge/projects/ibpp this is an Open Source direct
interface for C++, meaning that you don't need ODBC or DAO, or
OleDB, running interference. The docs are not great on this library,
but the code is solid.
VisualBasic, well I gave up on VB around V4, it;s Okay for small
projects, but it gets tougher to use on larger projects. Not to
mention that you need to rewrite copious amounts of code,
because Microsoft's VB team can't figure out how to depreciate
features, so if you wrote a program for V2.0 it was broken by (and
rewritten for ) 3.0, 4.0, 5.0, 6.0 and .Net. I have heard that .Net is
really good at this, it breaks almost all existing code.
The VisualC++ team can't figure out how to depreciate features
either, so they simply leave them in place, one of these years they
should go through all of the libraries, and release a document that
states certain features will disappear with the next version, and the
do a major code clean-up. Realistically the Kernel team needs to
do the same thing, even if it does break some code.
You could always go with Delphi, however if you don't know Delphi
or at least Pascal then that doesn't help much.
Paul
Paul Schmidt
Tricat Technologies
paul@...
www.tricattechnologies.com
> May be a little off topic: I am sold on Firebird and need haveGiven those two choices, go with C++, and surf over to
> several applications for it. Which is preferable programming language
> C++ or Visual Basic 6.
>
www.sourceforge/projects/ibpp this is an Open Source direct
interface for C++, meaning that you don't need ODBC or DAO, or
OleDB, running interference. The docs are not great on this library,
but the code is solid.
VisualBasic, well I gave up on VB around V4, it;s Okay for small
projects, but it gets tougher to use on larger projects. Not to
mention that you need to rewrite copious amounts of code,
because Microsoft's VB team can't figure out how to depreciate
features, so if you wrote a program for V2.0 it was broken by (and
rewritten for ) 3.0, 4.0, 5.0, 6.0 and .Net. I have heard that .Net is
really good at this, it breaks almost all existing code.
The VisualC++ team can't figure out how to depreciate features
either, so they simply leave them in place, one of these years they
should go through all of the libraries, and release a document that
states certain features will disappear with the next version, and the
do a major code clean-up. Realistically the Kernel team needs to
do the same thing, even if it does break some code.
You could always go with Delphi, however if you don't know Delphi
or at least Pascal then that doesn't help much.
Paul
Paul Schmidt
Tricat Technologies
paul@...
www.tricattechnologies.com