> A lot of the time using the vanilla API keeps you from coding in the > style most suited for a modern lang, which may only help introduce > bugs which the dev isn't used to worrying about. I don't think it's > right to recommend using it when there are wrappers tailored to keep > the dev thinking in their own lang.
> You certainly don't gain anything by using the flat API over a > wrapper, unless the wrapper is bloated/buggy! Problem with wrappers is, most of them are unfinished. The authors play with them to get some things work and forget about it after their problem has been solved. Minimal and complete libraries are non-trivial. Especially annoying is the situation, where the developer made a decision to use the wrapper and becomes confronted with missing functionality at some point in the future. The required thorough evaluation of the wrappers limitations might have been better spent in writing your own version ... Additionally, maintenance problems and dependencies (commercial or not) might occur, mostly things probably avoided from users of software in the style of sqlite (KISS as someone cited yet). Not touching Delphi for almost ten years - why not writing a minimal wrapper and extending step by step. I do it with my C++ wrappers routinely. It was most of the time the better solution in most aspects (time, simplicity). Micha --
