On 23 Sep 2014, at 8:25am, Prakash Premkumar <[email protected]> wrote:
> Thanks a lot for your opinion Hick. But the act of exposing struct Vdbe
> should be simple right. It's there sitting on my source code
Not really. It's there in someone else's source code. You're just compiling
that source code in your program.
> and my
> application needs to access it, just like it can access struct sqlite3
Your application should not be accessing the parts of a struct sqlite3. In
fact it shouldn't even know it's a struct. You're meant to declare variables
of type 'sqlite3' and pass them around from one function to another without
knowing what's in them.
> Can
> you kindly tell me how that can be done ?
There's a comment near the top of the source file 'vdbe.h' where it says
/*
** A single VDBE is an opaque structure named "Vdbe". Only routines
** in the source file sqliteVdbe.c are allowed to see the insides
** of this structure.
*/
typedef struct Vdbe Vdbe;
Emphasis on the word 'opaque'. Also, future versions of sqlite3 may change the
structure without warning. If you try to get at the internals of how SQLite
works you are going to have to learn ten times as much about SQLite as if you
were just going to use the documented functions listed in
<http://www.sqlite.org/c3ref/funclist.html>
and the fact that you needed to ask where those variable types were defined
suggests that you may not be ready to do that just yet.
Can you not do what you need to do using just the functions documented in the
above page ? Can you describe to us what you are trying to do in terms of your
program's requirements rather than in terms of how you think SQLite works ?
Simon.
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
