Excellent. I posted a question of development of sqlite in C++ long before. But this discussion benefited me and I think all those who depends upon C++ may have got a good direction. I am using sqlite with my own C++ wrapper since I am using VC++ to develop applications for last 5 years.
Thanks, Rajesh Nair. On 6/4/09, Sylvain Pointeau <sylvain.point...@gmail.com> wrote: > if I had to do a library, I would probably choose C++,at least the subset C > with classes. > > I will then export the main function as "C" > > many libraries are done like that now. > for example http://www.ode.org/ is mostly written in C++ but has an > interface in C > > I also use Qt because it has a clean API, > I find GTK very difficult to use and understand. > > I also found this article very interesting: > http://unthought.net/c++/c_vs_c++.html > > so I think there no good or bad choice, > probably sqlite made the best choice as this is now embed in so many > plateform. > > I would personally choose C++ if I had to do sqlite in 2009, > but I am not not able to do it, and it already exists :-) > (I use it every day) > > Cheers, > Sylvain > > > On Wed, Jun 3, 2009 at 5:23 PM, John Stanton <jo...@viacognis.com> wrote: > >> 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. >> > >> > >> This is something of a digression but is pertinent. Colleagues who >> worked with Bjarne Thorstrup (inventer of C++) tell me that Bjarne was >> disillusioned with C++ and its wide deployment and would encourage >> people not to use it unless there were clear advantages. >> >> In our own company we came to the same conclusion as Dr Hipp and used >> ANSI C for our compilers and database software. C can be anything you >> want it to be. For example you can ensure portability by incorporating >> your own memory management system and tightly manage your use of >> foreign libraries. for quality assurance You have access to highly >> optimizing compilers which can produce executables as good as those >> written by a skilled Assembler programmer. >> _______________________________________________ >> 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 > -- Regards Rajesh Nair _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
