Re: [Firebird-devel] Reference counters in API - was Re: Providers, yvalve, external engines and object lifecycle

[Daniel R. <da...@ac...>]

X-UCS- Spam Mail 2

Hi,

At March-30-11, 4:12 PM, Adriano dos Santos Fernandes wrote:


> Also:
> - Interfaces are something completely unknown for most Delphi
> developers. It's used only for interact with COM and somethings like
> shell objects (also COM) in the Windows API. It's completely unused in
> Delphi visual components AFAIK.

And, also to help develop an application with plugins(without using
COM). Also, interfaces are used in the VCL(although not everywhere),
and the data connectivity components.

> - It's sad that (if) Delphi creators still don't put in the language a
> way to support RAII decently.

I do agree here.  Yet, there is a way to implement it in a Delphi
interface.

> - We're create an API that almost no Delphi user will use directly. It's
> probably even many years to component creators starts using it. So it's
> okay to let them explicitly call a method to release an object, like
> they need to destroy any other object, cause they language don't support
> RAII.

Most Delphi developers wouldn't be using the Firebird API directly(at
least client side), they will be using third-party components that are
wrappers(i.e.: IB Objects, FIB Plus, UIB, etc...). The authors of
those components are most likely the ones that will be using the
Firebird API.

For the server side, I know that I most likely will be creating a
plugin for the security(authentication) that will be related to our
software, and most likely it will be developed using C++. And, the
main reason for using C++ in this case is that Delphi doesn't
currently support 64-bit development(although it is planned for later
this year, but I'm not holding my breath since it was on the roadmap
for the last 4 versions).

-- 
Best regards,
 Daniel Rail
 Senior Software Developer
 ACCRA Solutions Inc. (www.accra.ca)
 ACCRA Med Software Inc. (www.filopto.com)