lausobo

__attribute__((constructor))
void PIXWhatPartOfAdvertisingTrackingEnabledDidYouNotUnderstand(void) {
    if (![[ASIdentifierManager sharedManager] isAdvertisingTrackingEnabled]) {
        IMP newImplementation = imp_implementationWithBlock(^NSUUID *{
            return nil;
        });
        Method m = class_getInstanceMethod([ASIdentifierManager class], @selector(advertisingIdentifier));
        method_setImplementation(m, newImplementation);
    }
}

madx

DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
                    Version 2, December 2004

 Copyright (C) 2012 François Vaux <madx+github@yapok.org>

 Everyone is permitted to copy and distribute verbatim or modified
 copies of this license document, and changing it is allowed as long
 as the name is changed.

            DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE

akisute

import Foundation

class GrayShark {
    var name:String
    var howSwim:String
    
    init(name:String, howSwim:String) {
        self.name = name
        self.howSwim = howSwim;
    }

subdigital

xcode_proj=`find . -name "*.xc*" -d 1 | sort -r | head -1`

if [ `echo -n $xcode_proj | wc -m` == 0 ]
then
  echo "No xcworkspace/xcodeproj file found in the current directory."
  exit 1
fi

echo "Found $xcode_proj"
open $xcode_proj

hoshi-takanori

CLASS_NAME = MyObject
OBJS = main.o $(CLASS_NAME).o $(CLASS_NAME)Tests.o
PROGRAM = a.out

CFLAGS = -Wall -F$(FWPATH)
LIBS = -F$(FWPATH) -framework XCTest -framework Foundation

FWPATH = /Applications/Xcode.app/Contents/Developer/Library/Frameworks
XCTEST = /Applications/Xcode.app/Contents/Developer/usr/bin/xctest

nicklockwood

Thoughts on Swift 2 Errors

When Swift was first announced, I was gratified to see that one of the (few) philosophies that it shared with Objective-C was that exceptions should not be used for control flow, only for highlighting fatal programming errors at development time.

So it came as a surprise to me when Swift 2 brought (What appeared to be) traditional exception handling to the language.

Similarly surprised were the functional Swift programmers, who had put their faith in the Haskell-style approach to error handling, where every function returns an enum (or monad, if you like) containing either a valid result or an error. This seemed like a natural fit for Swift, so why did Apple instead opt for a solution originally designed for clumsy imperative languages?

I'm going to cover three things in this post:

tenderlove

#!/usr/bin/env ruby --disable-gems

# Tab completion for minitest tests.
#
# INSTALLATION:
#
# 1. Put this file in a directory in your $PATH.  Make sure it's executable
# 2. Run this:
#
#   $ complete -o bashdefault -f -C /path/to/this/file.rb ruby

lisamelton

#!/bin/bash
#
# convert-video.sh
#
# Copyright (c) 2013-2014 Don Melton
#

about() {
    cat <<EOF
$program 2.0 of December 3, 2014

lisamelton

#!/bin/bash
#
# convert-video.sh
#
# Copyright (c) 2013-2014 Don Melton
#

about() {
    cat <<EOF
$program 2.0 of December 3, 2014

jimbojsb

Step 0:

Get Homebrew installed on your mac if you don't already have it

Step 1:

Install highlight. "brew install highlight". (This brings down Lua and Boost as well)

Step 2: