It was one of the poorly thought through concepts which slipped into the
ash can of history without mourners.
To be reliable such a tool needs to be integrated into the development
system so that a change in schema forces a remake of all affected
applications. With discipline and the appropriate make files it is
theoretically possible to effect the integration.
Joe Wilson wrote:
Yes, a pre processor, but not a wrapper. A wrapper as I've seen from the
sqlite.org site is
simply a layer on top of the sqlite3 api. I've written my own wrapper. I'm
really looking to
see if instead of inserting an additional layer, the actual code could be
compiled inline into
the sourcing C file, thus a pre processor.
Okay, I see. All the bad memories are coming back now...
I used the PRO*C pre-processor ten years ago.
What a disaster that approach is. Never again.
The code is a mess and debugging is a nightmare.
You actually need a static database schema to run your code-generating
pre-processor against. You change your database schema and your code
generator has some obscure syntax error. If your application crashes
you have to wade through generated code to see WTF is going on.
In the time it takes to chase down problems you could have written
a superior application in a traditional language binding/wrapper.
Just my opinion of course.
____________________________________________________________________________________
Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
