release-builds

I know what ConditionalAttribute does. The docs say it can also be applied to a class, if it's derived from Attribute : [Conditional("DEBUG")] public class FooAttribute : Attribute { } But how does that custom attribute behave? (Is it stripped out of a release build?) @RicardoPontual's comment gave me an idea. I did this: [Conditional("DEBUG")] public class FooAttribute : Attribute { } [Foo] public class Bar { } I compiled in debug mode , and loaded the DLL in ILSpy (it's a disassembler). This is what I found, as expected: [Foo] public class Bar { } Then I compiled in release mode , and loaded

I'm building a shared library for use in a Java app using the Android NDK. Using readelf to inspect the lib/armeabi-v7a/libXXXlib.so file generated by a release build, it appears to contain all the symbols (function, variable names) of my native C/C++ code. Indeed, the shared object file appears to be identical for the debug and release builds. (The only difference in the output in the libs folder being whether or not the gsb.setup and gdbserver files are created.) I'm overriding the optimisation set by the NDK with an APP_CFLAGS += -O3 in my Application.mk , but I wouldn't expect the release

I have a class that creates an object lazily and stores it as a weak property. Other classes may request this object, but must obviously keep a strong reference to it to keep the object from being deallocated: // .h @interface ObjectManager @property(nonatomic, weak, readonly) NSObject *theObject; @end // .m @interface ObjectManager () @property(nonatomic, weak, readwrite) NSObject *theObject; @end @implementation ObjectManager - (NSObject *)theObject { if (!_theObject) { _theObject = [[NSObject alloc] init]; // Perform further setup of _theObject... } return _theObject; } @end When the scheme