Pointers in Slate.

[Brian Rice]

I don't know. You took on the responsibility for these decisions when 
you decided to write a backend. Read the code for files and how 
external identifiers are passed in and out. Maybe that will give you an 
idea (basically using asSmallInt), but you still have to make decisions 
based on how the system you're working on needs to behave - you might 
need an indirection table or a hash, or something else.

I'm a little disappointed that you've not finished the SDL backend 
first, or at least suitably presented it in a way that can be taken and 
used. So, what's the status of it? What functions work and are 
complete? Are there bugs? Are you still changing the source code 
heavily, or should I pick it up and start integrating it?

On Nov 10, 2004, at 10:44 AM, Pupeno wrote:

> I started working in a Cairo/X backend (I need a couple of xlib calls, 
> so, I'm
> making a backend for those calls as well). I'm making the xlib wrapper
> separatly of the cairo wrapper so if someone wants to use the xlib 
> wrapper
> and not use the cair wrapper, he/she can.
> I'm starting bit by bit... based on a cairo program that draws a 
> spline.
> The first thing the cairo program does is this:
> Display *dpy = XOpenDisplay(0);
> So I made a wrapper for XOpenDisplay... I pass a byte array to it that 
> is
> decoded to a char* (that 0 is a char*), but then, what do I do with 
> dpy ?
> Should I pass it back to Slate ? should I make an array of opened 
> displays ?
> I then will have a lot of other pointers... most of the time I don't 
> care
> what's inside... it is just for passing arround.
> Thanks.
--
Brian T. Rice
LOGOS Research and Development
http://tunes.org/~water/