Note that there are some explanatory texts on larger screens.

plurals
  1. USOverToasty
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. COYou can certainly "get-by" for a while in Obj-C without knowing much "hard C", but you'll never play pro-ball. However, C is procedural and Obj-C is OOP - so spending years "learning C first" is also a bad idea, as it's a different way of doing things, though eventually you'll have to learn both. For now, what you really need is to learn "Just Enough C" to get past this barrier. I strongly recommend "Beginning Mac OX Snow Leopard Programming", chapter 6 "The C Programming Language", which it explains in this context - it's a little out of date - but it's still great to get you over this hump.
      singulars
    2. COJust checked it out - as expected, it's great for going from C++ to Obj-C ( though it's from 2009, and things have changed a bit ), however, when it mentions key differences between C++ and Obj-C - it assumes you already know the C++ side of the difference, and does little more than jog the memory to explain it, it primarily focuses on the Obj-C side - which you already know - this sadly, limits its usefulness. In short, C++ to Obj-C explanations are not symmetric with Obj-C to C++ explanations.
      singulars
    3. COA great way to check if the sampler is playing on the simulator but NOT on the device, is to clean and run the simulator, then find the app bundle it created ( generally in ~/UserAccount/Library/Application Support/iPhone Simulator/6.0/Applications/RandomAppNumber/AppNamePkg ) right click on the Application Package, and select "Show Package Contents", if there's no officially named folder in there like "Sounds" with the correct samples inside it, even IF the correct samples are in the package but NOT inside a "Sounds" or "Sample Files" dir, then it won't play on the device but will in the sim
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload