Joe Groff

@jckarter last time I did it was to return something other than self from a constructor. This was totally valid in Obj-C...

@Javi A protocol extension initializer can reassign self, if that's the only reason you needed ObjC.

@jckarter kind of, but I needed that to be the designated initializer :-/

@Javi To be able to super.init, it'd need to allocate the new object as the dynamic type but only allocate the base class part of the object

@jckarter @zedshaw I used an ObjC bridge to get values from GCC_PREPROCESSOR_DEFINITIONS in a Swift CLI... is there a better way?

@ndrewmcknight @zedshaw For macros we don't import, a C shim's your best bet. If it's just a binary flag you might try swiftc -D and #if.

@jckarter @zedshaw I'm intrigued by this C shim. Could you show an example?

@rodbrown88 To help with that, Xcode can generate an interface from Swift files, under the assistant view as "Generated Interface".

@jckarter @zedshaw Answered “no”, but I guess objc_msgSend is not possible from Swift

@Tricertops Not directly. 'performSelector' or dynamic dispatch via AnyObject should be able to generate any msgSend you'd need.

@jckarter @Tricertops Isn't `performSelector` not available in Swift? I thought it and NSInvocation were marked as unavailable.

@jckarter @zedshaw A fetched objects class was MyEntity_MyEntity_, instead of just MyEntity. Ob-C [object class] solved it

@matt_sven @zedshaw I think it's intended to be namespaced by the app's module name, but 'Module_Name_' sounds weird. cc @UINT_MIN

@matt_sven Would definitely like more details here about the non-working code, if there are any to be had. // @jckarter

@UINT_MIN @jckarter [fetchedObject class] returns the right class in Obj-C. Am passing the fetched object to Obj-C and calling -class as fix

@matt_sven @UINT_MIN Does fetchedObject.dynamicType produce the right class object in Swift?