I’m probably just mistaken then. Jon was responsible for the parser implementation and details of Honu, and I have forgotten what I knew. Jon might have had a specific reason to use an explicit stack, or maybe it was just the way he chose to implement it.

If you have a plain _pointer and you want to treat it as a C struct pointer to _T so you can use T accessors, then probably you want (_cast ... _pointer _T-pointer). But (_ptr-ref ... _T) should do the same thing, so maybe I misunderstand what you’re trying to do. A (_ptr-ref ... _T-pointer) would be different.

thank you for your response! it worked… then it didnt, idk what im doing wrong, i pasted it in a https://gist.github.com/kurinoku/3361da78d2d6fb1763eea99696ba40dc\|gist . idk if you have windows, im assuming you dont… but any help is appreciated

soo… https://docs.racket-lang.org/foreign/foreign_pointer-funcs.html#%28def._%28%28quote._~23~25foreign%29._malloc%29%29\|malloc documentation in ffi/unsafe does not seem very coherent, it also doesn’t help that in Overview from that same library the examples calls do not match the definition.

@soegaard2 What does import in urlang do?

It currently seems to do nothing.

At first I thought it was import/export for ES6 modules, but it seems like urlang doesn’t support ES6 modules at all?

It’s been a while since I worked with HBITMAPs, but isn’t that a handle that’s opaque, and where you have to use functions like GetObject to extract bytes? In case it helps, here’s some code that involves HBITMAPs: https://github.com/racket/gui/blob/master/gui-lib/mred/private/wx/win32/hbitmap.rkt. The hbitmap->bitmap function uses GetObject to extract a BITMAP from an HBITMAP.