Re: guile-gtk?



Daniel Barlow <dan@telent.net> writes:

> Are there speed considerations which would bias it either way?  If I'm
> looking at pointer motion events, for example, I'm probably getting
> quite a lot of them, and I probably want to get at least x, y and
> button status information: are three calls into C code more or less
> expensive than one to build an alist and then call assoc a lot?

One consideration is consing the alist. It will be pretty long (look
at the x event structure sizes) and there will be a lot of them.  This
means gcfest. Accessors don't have this problem.

I think it's best to go with both.

-- 
I refuse to use .sig



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]