Plausible Blocks Development Google Group

Xcode 4.2/iOS 5 SDK compatibility?

2011-10-14T23:37:33Z

Is there any update on the status of PLBlocks compatibility with XCode 4.2 and/or the iOS 5 SDK? There hasn't been any activity on the Google Code issue since early September. It looks like Apple has released the relevant sources on their Open Source site; is it just a matter applying the patches and recompiling? I'd love to help get this working, but the checkout instructions on the Google Code site point at a URL that doesn't exist...

Unsupported Compiler error in Xcode 4.2 beta 6

2011-08-19T22:09:03Z

I know it's beta, but I just thought I'd send a heads up... it looks
like Xcode 4.2 beta 6 won't compile projects with the PLBlocks
compiler:

Check dependencies

Unsupported compiler 'GCC 4.2 (Plausible Blocks)' selected for
architecture 'armv7'
Unsupported compiler 'GCC 4.2 (Plausible Blocks)' selected for

Xcode 4/iOS SDK 4.3 simulator builds fail with 1.1b7

2011-03-10T03:45:34Z

Anyone managed to get simulator builds to work in Xcode 4 & iOS SDK 4.3
*What steps will reproduce the problem?*
1. Open an Xcode 4 project (iOS 4.3)*
2. Attempt to build with PLBlocks
* Tried with both an existing and a new project.
*What is the expected output? What do you see instead?*
Should build. Doesn't. Errors in some UIKit classes.

PLBlocks in Xcode 4

2011-02-07T20:29:15Z

Has anyone been able to get PLBlocks 1.1.1 SDK working with Xcode 4? I
installed the SDK in my Xcode 4 /Developer directory and attempted to open
an existing project using PLBlocks, but it won't compile as it doesn't know
how to resolve PLBlocks as a valid compiler. It appears to be an Xcode 4

C++ support

2011-02-04T08:53:45Z

I see various messages saying PLBlocks is not compatible with C++, but
this has two interpretations and I am not clear which it really is.

a) You can't compile a project that contains any .mm files at all if
you use PLBlocks.

b) You can't use blocks from C++ functions, nor C++ calls from inside

Link errors with Plausible Blocks runtime 1.1b6 and above

2010-11-06T23:02:56Z

Hi,

I'm seeing link errors when I try and use versions of the Plausible
Blocks runtime that incorporate the "Added experimental support for
delegating to Apple's runtime if it is available and supported"
feature mentioned in the changelog. The errors look like this:

"""
Undefined symbols:

Investigating PLBlocks

2010-10-07T16:11:06Z

I've been investigating using PLBlocks on an iPad project as a way to
maintain backwards compatibility with 3.2 as we migrate to iOS 4.2.
It appears to work well with both the current OS and the 4.2 beta, but
have a couple questions before I recommend this as a solution to my
client:

1) The FAQ says it's used by quite a few shipping applications. Could

Is there a way to build or at least debug on 10.5?

2010-10-03T19:57:23Z

Trying to figure out if there is a way to build and or debug on 10.5
with pl-blocks

Understanding of Block stack

2010-09-27T00:26:54Z

Hello,

I'm facing a strange issue in a part of my code that is heavily
dependent on PLBlocks, and I wonder if I may inadvertently be
modifying program memory somewhere else. I wasn't sure where to ask --
I hope this is all right.

I am performing a search on a database. The actual search function

Clang patch...

2010-09-16T16:25:08Z

Hey people, I have a little patch for clang to make it work with
PLBlocks... Sadly it's only proven to work when compiling for the
device, I'm not sure to understand the problem when compiling for the
simulator...

It seems that the symbol changes are not even taken into account...

So here's the diff, from tools/clang/...

LLVM + Plausible Blocks Runtime

2010-09-06T15:32:33Z

Hey guys,

First of all, awesome job. I've been using plblocks for a while, and
it's great. I modified many of my "framework" classes to use blocks
instead of delegates, and I find it much more intuitive.

To my question: I have a client that wants to use the "official" LLVM
compiler, and run in iOS3 devices. If I use my existing code in iOS3,

PLBlocks 1.1Beta 5 is broken in iOS 4.1 GM

2010-09-03T19:11:23Z

It seems Apple change something how it compiles these objective-c
files.

I checked with GCC 4.2 - compiles just fine
PLBlocks one - 1347 errors

something is like one for error: expected declaration specifiers
before and a ton of error: storage class specified for parameter

I am using Xcode 3.2.4 for it.

PLBlocks 1.1b6 + iOS4 SDK Target + 3.1.3 deployment target + Objective C++ == SIGSYS

2010-07-30T17:07:23Z

Hi!

I can't get PLBlocks to run with my code. It just goes SIGSYS...

#0 0x003ec384 in _PLBlock_object_assign at Block.m:538
#1 0x003ec364 in _PLBlock_copy_internal at Block.m:341
#2 0x003ec5ea in _PLBlock_copy at Block.m:128
#3 0x003ebd38 in -[PLBlock copyWithZone:] at NSBlock.m:56

PLBlocks doesn't seem to be working

2010-07-30T15:17:24Z

Hey guys. I'm playing around with blocks. I have a simple app I made
to learn them and of course I'm hooked. My next step was to make sure
I can support iOS 3.0+ with my code by using PLBlocks.

I installed the sdk, i'm compiling with the PLBlocks flavored gcc, and
I've added the 1.1 framework to my code, but still can't get blocks to

LLVM and XCode 4

2010-07-22T23:51:37Z

I noticed that it seems with XCode 4 Apple is emphasizing LLVM as the
compiler of choice. Is this going to effect PLBlocks especially
targeting iOS 3.2?

5 consistent build errors

2010-07-01T03:41:22Z

I am seeing five build errors when using plblocks. I see them on two
different computers. I tried upgrade to 1.1-beta5 and still see them.
Interestingly, a co-worker of mine is not seeing them on his computer
running the same code from the same git repo. I have installed the
plblocks sdk and copied & linked in the iPhone runtime

Porting to iPhone 4.0 SDK

2010-06-18T10:00:09Z

Hi all,

The new Apple way of things suggests to use the latest SDK (that is
4.0) and set the deployment target to minimal compatible (and resolve
any feature issues in run time). My application (based on 3.1 SDK)
makes a heavy usage of plblocks, and I want to port it to 4.0. The
problem is that I cannot use any bundled compiler and native blocks,

Download Corrupt

2010-06-09T21:31:01Z

I am trying to mount the PLBlocks 1.1 Beta 5 image but it show errors
that said "not recognized."

PLBlocks 1.1-beta2 Released

2010-02-08T18:39:21Z

Hello All --
I've just released PLBlocks 1.1-beta2 on Google Code (1.1-beta1 was not publicly released). This new release adds support for:
- C and C++ development
- Objective-C Garbage Collection
The 1.1 compiler remains compatible with the existing PLBlocks 1.0 runtime, but use of new features (garbage collection, C/C++ support) also requires using the PLBlocks 1.1+ runtime.

GC build of Framework

2010-02-04T22:04:21Z

Hi,
I have successfully built against version 1.0 of the PLBlocks
Framework. However, my app uses GC.
So I need to rebuild the Framework with GC support.
Has anybody done this and does it work?
Joubert

Struggling to build app that links to PLBlocks - errors in precompiling AppKit.h

2010-02-04T17:53:02Z

Hi,
I am building on Snow Leopard.
I have the "PLBlocks Snow Leopard SDK installed".
I created a new Target, which:
- links to PLBlocks.framework
- is set to use the PLBlocks GCC
However, when I build this target against the the 10.6 SDK, the
precompilation step of AppKit.h results in 34117 errors.
e.g., for: "@class NSString, Protocol;" the compiler says: "Expected

Is there a Block enhanced iPhone API library?

2010-01-23T11:40:17Z

Got PLBlocks running on an iPhone project, and it is glorious. But
I'm noticing that everywhere that I would want to use a block, I need
to extend an existing class in order to do it.
So I am wondering if there is a open source project somewhere that
block-enabled many common tasks in the iPhone SDK that I could

Possible OT: Objective-C Memory Visibility Rules

2010-01-04T21:55:15Z

I'm a new objective-C developer coming from a Java concurrency
background. I'm all too familiar with the memory visibility pitfalls
that can occur when 'happens-before' semantics are not guaranteed.
I've been googling for a while now (on and off for the past few weeks)
trying to find equivalent rules for Objective-C. I'm guessing you

Re: Blocks not working with instanceMethodSignatureForSelector

2010-01-03T22:10:45Z

Hey Stuart --
I wasn't able to reproduce this locally (using the 3.1.2 SDK, PLBlocks 1.0) -- I included my app delegate source below.
Is the category defined in a static library, and -ObjC isn't being passed to the linker? Does otool -v -V -o on the binary show the expected category methods?
Thanks,

How hard would it be to enable Static Analysis with PLBlocks?

2009-11-24T03:29:15Z

I've been using PLBlocks for a while now in my iPhone app and it's
working great; it really helped simplify my code. I recently noticed,
though, that my static analysis steps were failing with a message of
"Analyzer skipped this file due to parse errors". It's pretty clear
that the parse error in question is my block type definition:

Thanks

2009-11-02T01:56:05Z

Landon, just wanted to say thanks for your efforts. I'm incorporating
this into an existing iPhone project, and very much enjoy the benefits
of closures. I'm using blocks with the ASIHTTP* project, and do plan
on releasing the source code in the future.

Cheers,

Stu

UIViewController with a Nested Block Question

2009-09-17T22:52:45Z

I was wondering what possible mechanisms could be put into place to
avoid accessing an object that has been dealloced. The situation is
something like this:

- UIViewController is instantiated and a method is called that runs a
block on a background thread that has a nested block the runs on the

Re: Lets get acquainted

2009-09-17T00:14:23Z

The best spam I've got!
We have so many questions of GCD, agreed..

Garbage Collection Support Testing

2009-09-12T20:40:17Z

I've just committed support for Mac OS X garbage collection to trunk.
I had to make a few small compiler fixes to support __weak __block
variable references, so GC will require installing a new toolchain:
cd Compilers && ./bin/build.sh --compiler gcc42-macosx10.5 --
destroot /Developer/Library/PLBlocks/Co mpilers/gcc42-macosx10.5

Problem compiling with C++ files

2009-09-08T08:28:32Z

Hey,

If you're unlucky enough to need to compile with the C++ compiler (one
of my projects has a single .mm file to help link a C++ library into
my code) then Xcode dies trying to compile with the wrong path for g+
+. It was trying to access

/Developer/PLBlocks/Compilers/ g++42-macosx10.5/usr/bin/gcc-4 .2

PLBlocks 1.0 Released

2009-09-06T20:54:11Z

Hello All --
I've just released PLBlocks 1.0 on Google Code. There are no runtime
changes from 1.0-beta2, but the following minor compiler and
installation package changes are included:
- Fixed support for using pre-compiled headers with blocks.
- Work-around for rdar://7189835 - Xcode rewrites all occurrence of

Can't figure out how to link

2009-09-04T22:34:15Z

I wanted to play around with Apple's new blocks feature, so I
downloaded the plblocks bundle, and tried to follow the directions.
I've never used Xcode before, so it's possible that I'm doing
something dumb, but I just keep getting linking errors. Specifically:

cd /Users/ben8/BlocksTester

Difference between Snow Leopard & Leopard SDKs..?

2009-08-28T02:07:33Z

This should probably be obvious, but I wasn't able to find an
explanation for this.

What is the difference between the 10.5 and 10.6 versions of the SDK?

If one is developing on 10.6, but wants their app to run on 10.5, does
that mean they should make sure to use the 10.5 version? If so, what's

Using PLBlocks while using 10.6 SDK, but MACOSX_DEPLOYMENT_TARGET 10.5?

2009-08-21T04:56:18Z

Hi guys,

I have an app that I'm testing right now that could really benefit
from blocks, but I have the situation as stated in the title - I
compile and develop against the 10.6 SDK, but target 10.5 as the
deployment version. Is there a supportable way to get blocks in this
app under both Leopard and Snow Leopard, or am I going to have to

Blog post on blocks featuring PLBlocks

2009-08-14T22:11:07Z

As Landon requested, I did this week's Friday Q&A on blocks, as a
followup to my original post from this past winter. PLBlocks, as the
only reasonable way to work with blocks without using an NDA'd
product, features heavily. You can get to it here:

[link]

Error building if blocks appear in pre-compiled prefix header

2009-07-26T19:35:28Z

I'm not sure if anyone else has run into this issue, but it seems that
if I use a pre-compiled prefix header that includes a file containing
block definitions (e.g., if I make some NSThread or NSArray extensions
and include these in my prefix header) *and* the prefix header is pre-
compiled, the plblocks compiler can't deal with it. I end up with the

Where to obtain Apple's source for gcc 4.2

2009-07-13T22:42:24Z

Would someone mind directing me to Apple's gcc 4.2 (OS 3.0 SDK) source
to apply the diff's?

Any assistance would be greatly appreciated.

Cheers,

Stuart

PLBlockOperation and isConcurrent

2009-07-12T18:33:37Z

Hi guys. Killer backport, Landon. I really appreciate the work you're
putting into this.
warning: I'm new to blocks in objc, so I could be speaking from my less
sanitary areas.
I'm running into a problem using the PLBlockOperation object that is, I
think, stemming from the block running concurrently while returning the

Memory management considerations?

2009-07-09T01:06:53Z

First, thank you for doing this, and for making it open source.
Absolutely incredible work and I can't wait to play around with it,
although at the same time I'm dreading thinking about the amount of
code that I may end up totally rewriting because of the existence of
blocks for 10.5...

That said, blocks seem to be a really new concept (for ObjC) with not

iPhone OS 2.2 support?

2009-07-07T21:46:38Z

Hi,

I just about danced a jig when I saw that you'd ported blocks to
iPhone OS. My language of choice is OCaml and writing all those
delegate methods for silly things like action sheets has been sheer
agony. I can't tell you how many times I've had to bite my tongue to
keep from screaming "this would be so damned easy with higher order

Failure log

2009-07-03T21:01:21Z

Compilers: gcc42-macosx10.5
Building gcc42-macosx10.5
+ TRANSLATE_ARCH='sed -e s/ppc/powerpc/ -e s/i386/i686/ -e s/armv6/
arm/'
++ echo i386
++ sed -e s/ppc/powerpc/ -e s/i386/i686/ -e s/armv6/arm/
+ HOSTS=i686
++ echo i386 ppc
++ sed -e s/ppc/powerpc/ -e s/i386/i686/ -e s/armv6/arm/
+ TARGETS='i686 powerpc'

PPC support?

2009-07-03T14:09:33Z

First, great work. I haven't actually tried it out yet, but I really
like how you've integrated it so smoothly into Xcode.

I was wondering about PPC support in the SDK itself, i.e. building
blocks code on PPC, not just for PPC. Would this just be a matter of
recompiling with the right architecture, or is there something more