OpenEuphoria

Re: SQLite wrappers

• Posted by "Kat" <gertie at visionsix.com> Aug 24, 2005
• 588 views

On 24 Aug 2005, at 6:40, Jason Gade wrote:

>
>
> posted by: Jason Gade <jaygade at yahoo.com>
>
> Tone =8Akoda wrote:
> >=20
> > jacques desch=EAnes wrote:
> >=20
> > > Search the archive for eusqlite
> >=20
> >=20
> > i already did that, those wrappers are incomplete. and sqlite_exec() do=
esn't
> > work, i don't know why. anyway i am going to do the wrappers for those
> > additional functions and since c pointers are still blurry to me i made=
 me
> > this tutorial to clear them up: <a
> > href="http://www10.brinkster.com/tskoda/C_pointers_explanation.htm">h=
ttp://www
> > 10.brinkster.com/tskoda/C_pointers_explanation.htm</a> maybe someone wi=
ll find
> > it helpful.
> >=20
>
> Okay, now explain pointers to pointers, arrays of pointers, and of course=
 arrays
> of pointers to pointers... not to mention pointers to functions 

In a cpu like the 6502 (as if there is anything comparable) which has only =
3
user registers (one 8 bit and 2 for either 8 or 16bit) , we used all of zer=
o page=20
as pointers (to pointers (to pointers)). Zero page (all 256 bytes of it) wa=
s
offsets or direct pointers to other stuff. Or even indirect offsets to poin=
ters,=20
data, or code. I thought of them as scratchpad cpu registers located off th=
e
cpu. Pointers are as easy as goto, and can be just as useful. They are grea=
t
for re-typecasting, such as using an [array of chars] as a [C-string] and a=
s a=20
[basic string] all at the same time. And it would beat breaking a flat 32bi=
t
integer into 8 bit bytes, simply by pointing to the 4 bytes. Or using a 32b=
it
integer as an array of booleans. Or an 8bit byte as a fuzzy boolean. When=

switching to pascal, i often had arrays of pointers. Eu solves a lot of tho=
se
"problems" with sequences tho.=20

Kat