***wleslie__ is now known as wleslie
<stis_>hmm, modding a gc is insanely difficult <stis_>I'm only getting it to work inferiorly <stis_>e.g. it has to do insanely many gc sweeps to clean the data <wingo>i finally have a fix for the n^2 memory issue <wingo>working on cleaning it up, will push shortly <wingo>a relief; been sitting on that for weeks now <mgsk>wingo: what's going on with this year's guile emacs? The repo doesn't seem to have been updated since last yeear. <daviid>dsmith-work: how are things and hacking? <daviid>dsmith-work: of topic, someone here mentioned another sd card type computer, not the rasbery pi, not the beagle bone, but another that was indeed also coming with its container [not just the mother board], do you remember its name? <daviid>guilers, anyone has cairo experience, as in used to draw using guile-gnome? <daviid>dsmith-work: did search already but there is no search facility oer say, have to parse day per day... <daviid>it is terrible actually, am i wrong? <dsmith-work>Hmm. Must have been rotty who had the searchable logs then. <daviid>out of curiousity, why did we wrote g-wrap instead of using swig? <dsmith-work>istr that they came out about the same time. Maybe g-wrap was first? <daviid>i like g-wrap better actually, (1) it's fully integrated in guile, and (2) it makes extensive use of goops <daviid>till now i thought basic types where managed [by g-wrap] in such a way that we got pointers to them 'for free', there apparently still is something I am missing I guess. I have 'opaque type warnings' for functions [guile-gnome, guile-clutter] returning double*, guint8*, gunichar* [unsigned-int32*] and gunichar2* [unsigned-int16*, which surprises me: is this expected?