Working with Dynamic Libraries in Xcode

Here's just a little tidbit that I ran across recently where Xcode, which normally does a good job covering all the bases, fell short just a bit. When you're working with dynamic libraries in just about any environment, especially Linux and MacOS, there is a two-way street when it comes to a program or another … Continue reading Working with Dynamic Libraries in Xcode

Swift – First Impressions

After playing with Swift a bit here are my first impressions of the language. There is definitely a lot to like about it! There's also a few things that annoy me. 😎 But first I'll start out with a giving you a 1,000 foot overview of the language itself. Syntax aside, Swift and Objective-C 2.0 (as … Continue reading Swift – First Impressions

Taking the Swift Plunge

Okay... So... I think I'm finally ready to take the plunge and start learning the Swift Programming Language in earnest. I've been watching it and starting with version 5 there is finally enough there for me to get excited about. But this isn't going to be easy for me. Not like it was when I … Continue reading Taking the Swift Plunge

Rubicon

I've made a major milestone in my personal project Rubicon.  I've gotten it where it will build on Linux as well as Mac OS X.  More info is in the readme file.  Check it out: https://github.com/GalenRhodes/Rubicon

Always an Easier Way

Previously in Avoiding an Objective-C Pitfall #1 I discussed a more stable way of creating singletons in Objective-C.  As with all things in the world of Apple there's always an easier way and that way comes to us via two very powerful yet unnoticed (in the Windows and Linux communities at least) APIs that Apple has contributed to … Continue reading Always an Easier Way

Avoiding an Objective-C Pitfall #1

Below is a very commonly used design pattern in Objective-C. It's the typical Objective-C "Singleton Pattern" because it does just that.  Returns a singleton of the class it belongs to.  If we take a look at an example that uses it we can see it in action. The "@synchronized(self)" statement ensures that only one thread at a … Continue reading Avoiding an Objective-C Pitfall #1