search for: block_copy

...generally, on Mac OS X, the blocks runtime is linked into the C library ("libSystem"), and available to the entire OS. Clients that create blocks may implicitly get compiler-generated calls to some of the runtime functions, and the developer may also make explicit calls to, e.g., Block_copy(). On other OSes, the library would need to be built and installed somewhere. There's also the question of whether it should be a shared library or static library. I can see both points, but think that a shared library is probably the right way for it. It should probably be generally po...

...ams seem to work at that point for me: $ cat foo.c #include <stdio.h> #include <stdlib.h> #include <Block.h> int main(int argc, char *argv[]) { int x = 123; void (^printXAndY)(int) = ^(int y) { printf("%d %d\n", x, y); }; void (^copyPrintXAndY)(int) = Block_copy(printXAndY); copyPrintXAndY(456); // prints: 123 456 Block_release(copyPrintXAndY); return 0; } $ clang -I$PREFIX/include -fblocks -c foo.c $ clang -L$PREFIX/lib -Wl,-rpath,$PREFIX/lib -o foo foo.o - lBlocksRuntime $ ./foo 123 456 $ I've also tried similar steps on Ubuntu Linux,...

Good day, I been working on the CMake build system (which is nice and portable) + code clean ups over the whole Compiler-RT software suit. I recently added Blocks to the CMake build system but there is some ugly looking warnings I need to fix up in the Blocks code which I have not had time to look into yet. N.B. The CMake build system is not complete yet due to my lack of time, however I am still

Hi folks, So, various folks are in the process of porting Grand Central Dispatch to FreeBSD (c.f. http://libdispatch.macosforge.org and http://lists.macosforge.org/pipermail/libdispatch-dev for mailing list discussion on the topic) and are making good progress, but one of the issues they're running into is support for Blocks in FreeBSD. On the one hand, they could try and back-port