User Profile

Post marked as solved

Click to stop watching this thread.

You have stopped watching this post. Click to start watching again.

3 Replies

contentPostList.repliessolved.tooltip

Replied In experimental/coroutine

i was able to do that specifying -fcoroutines-ts in other C++ flags of Xcode. C++17

Post not yet marked as solved

Click to stop watching this thread.

You have stopped watching this post. Click to start watching again.

62 Replies

contentPostList.repliesup-voted.tooltip

Replied In AVAudioSessionErrorCodeCannotStartRecording when recording in the background with iOS 13

+1 ;-(

Post not yet marked as solved

Click to stop watching this thread.

You have stopped watching this post. Click to start watching again.

11 Replies

contentPostList.repliesup-voted.tooltip

Replied In NSDictionary != NSMutableDictionary

weird... i even enabled "pedantic warnings", "treat incompatible pointer types warnings as errors" and "treat warnings as errors" and still no joy. tried different "C language dialects" as well. can you reveal the exact warning message in the build window, and post here the message - if there's a "code" in brackets i might be able putting it as an explicit "Werror" in the project.

Post not yet marked as solved

Click to stop watching this thread.

You have stopped watching this post. Click to start watching again.

11 Replies

contentPostList.repliesup-voted.tooltip

Replied In NSDictionary != NSMutableDictionary

not even the above, even this:void foo(NSMutableDictionary** mutableDictionary) { (*mutableDictionary)[@"hello"] = @"world";}... NSObject* whatever = [NSObject new]; foo(&whatever); // no compilation error or warning here! obvious runtime crash down the roadlooks like any superclass pointer causes this behavior. quite dangerous behaviour.Animal -> Dog -> Labradorvoid labradors_only_here_please(Labrador** labrador) { [*labrador whatever_only_labradors_can_do];}Dog* generic_dog = [Dog new];labradors_only_here_please(&generic_dog) // ok cap, no problem... boom, crash