seems some systems just create a null pointer if youre creating data of count 0 via foreign-alloc. this makes sense. dont know why i did :count 0 in the first place, but changing it to 1. still broken on ECL in windows, though, but im starting to think ecl/cffi on windows dont mix too well yet...
seems some systems just create a null pointer if youre creating data of count 0 via foreign-alloc. this makes sense. dont know why i did :count 0 in the first place, but changing it to 1. still broken on ECL in windows, though, but im starting to think ecl/cffi on windows dont mix too well yet...

orivej/cl-async,orthecreedence/cl-async,Drooids/cl-async