Re: Low level C interaction (Specifically OpenGL)

Thanks a lot for that. Am I best to just macro up the (sys:sap-int
.....) call to something like (address-of points), and then make the
macro portable later?
I am a little concerned for portability - I generally try to write
fairly portable C code - should I try to write these kinds of things
using UFFI/CFFI, macro wrappers (my own portability layer), or not even
bother at all for now?

Thanks again - I'll probably have many more naive questions :)

Brad

.

Relevant Pages

  • Re: File paths
    ... but the macro replacement is an easier way to get the same effect ... > Hardcoded file names are among the common portability problem I have ... But the macro substitution can be included with a portable application ...
    (comp.lang.forth)
  • Re: Atomic operations in 32 and 64 bit platforms
    ... Great for reducing negatives. ... portability between OSes and other resource sets. ... GAS has no macro facilities, but some are added by GASP. ...
    (comp.lang.asm.x86)
  • Re: Math::Pari Failed Tests
    ... Ryan wrote: ... Lfor more on portability concerns. ... Fort Worth, Texas ... Prev by Date: ...
    (comp.lang.perl.misc)
  • Re: BBC expands DAB footprint by 1.2 million
    ... I have a 3 ele pointing to CP/Croydon which is usually fine but no chance of ... any portability etc. ... Lewis ... Prev by Date: ...
    (alt.radio.digital)
  • Re: BBC expands DAB footprint by 1.2 million
    ... I have a 3 ele pointing to CP/Croydon which is usually fine but no chance of ... any portability etc. ... Lewis ... Prev by Date: ...
    (alt.radio.digital)