yes true,
case closed then !

Many thanks for all of your answers.

Cheers,
Sylvain

On Wed, Jun 3, 2009 at 12:17 PM, P Kishor <punk.k...@gmail.com> wrote:

> On Wed, Jun 3, 2009 at 5:02 AM, Hamish Allan <ham...@gmail.com> wrote:
> > On Wed, Jun 3, 2009 at 8:59 AM, Sylvain Pointeau
> > <sylvain.point...@gmail.com> wrote:
> >
> >> I can perfectly understand the decision made few years ago,and the
> result is
> >> splendid, I use SQLite every days.
> >>
> >> I am just wondering why not introducing C++? for better memory
> management
> >> for example (RAII)
> >>
> >> I am just wondering, don't reply aggressively please ...
> >
> > If you keep asking when you've already received a perfectly good
> > answer (about portability), people will start to think you're trying
> > to start an argument (about memory management).
>
> Indeed. Very good reply.
>
> To Sylvain, once again: speculating on what went into the minds of the
> developers, when they set out to develop SQLite, they chose the best,
> most concise, most portable, most universally compilable, mother of
> almost all languages. Once they developed something that was free,
> fast and cheap, there was no reason to change. Case closed.
>
> If you thing C++ can do a better job at doing what SQLite does on all
> the variety of platforms that it runs on flawlessly, well, the source
> code is available in public domain -- go ahead and create SQLite++ by
> transcribing each function into the language of your choice.
>
> May the better plan win.
>
>
> --
> Puneet Kishor
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to