Kosuke Matsuda matsuda

Here's my own list of the interesting stuff announced during this year's WWDC, collected from the keynotes, various Apple docs, blog posts and tweets.

If you're planning to watch the videos, I really recommend this Mac app that helps you download and watch them: https://github.com/insidegui/WWDC.

OS X El Capitan

http://www.apple.com/osx/elcapitan-preview/

split view - two apps side by side on full screen

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:

#Every Single Option Under The Sun

optimization level options
automatic crashing options
debug info options
swift internal options
swift debug/development internal options
linker-specific options
mode options

Swift Don'ts

Don't add code cruft. Avoid parentheses around conditions in if-statements or with the return keyword. Don't add semicolons except where syntactically demanded in statements or to separate statements on the same line.
Don't use ALL_CAPS; use camelCase
Don't fight type inference. Use enumeration prefixes, self-references, and class names (with constructors) only when necessary or to clarify coding intent.
Don't use var when let is appropriate, especially for properties. The compiler better optimizes let statements for items whose values will not change during their lifetime. For example, Apple writes, "It is good practice to create immutable collections in all cases where the collection does not need to change. Doing so enables the Swift compiler to optimize the performance of the collections you create."
Don't use classes when structs will do. Use class

~~未修正のアプリが数多く残っている状態なので、パブリックな場所での言及には注意して下さい~~

未修正のアプリが数多く残っている状況ですが、すでに広く情報が公開されており、2.5.2で修正されたという情報が広まると混乱が生じるため広く周知する次第です。

問題と経緯

AFNetworking 2.5.1 にMITM攻撃を許す脆弱性があり、2.5.2で修正された、と報道されていますが、これは誤りです。

http://blog.mindedsecurity.com/2015/03/ssl-mitm-attack-in-afnetworking-251-do.html

	------------
	Conformances
	------------

	protocol AbsoluteValuable
	Conformances:
	Comparable
	IntegerLiteralConvertible
	SignedNumberType

	import Cocoa

	// Note: use of enumeration var in generic is instadeath
	// Note: use of static var in generic is not yet supported

	public protocol EnumConvertible: Hashable {
	init?(hashValue hash: Int)
	static func countMembers() -> Int
	static func members() -> [Self]
	}

	@implementation UIView (PSPDFKitAdditions)

	- (UIViewController *)pspdf_closestViewController {
	UIResponder *responder = self;
	while ((responder = [responder nextResponder])) {
	if ([responder isKindOfClass:UIViewController.class]) break;
	}
	return (UIViewController *)responder;
	}

	#!/bin/sh

	UNIVERSAL_OUTPUTFOLDER=${BUILD_DIR}/${CONFIGURATION}-universal

	# make sure the output directory exists
	mkdir -p "${UNIVERSAL_OUTPUTFOLDER}"

	# Step 1. Build Device and Simulator versions
	xcodebuild -target "${PROJECT_NAME}" ONLY_ACTIVE_ARCH=NO -configuration ${CONFIGURATION} -sdk iphoneos BUILD_DIR="${BUILD_DIR}" BUILD_ROOT="${BUILD_ROOT}" clean build
	xcodebuild -target "${PROJECT_NAME}" -configuration ${CONFIGURATION} -sdk iphonesimulator ONLY_ACTIVE_ARCH=NO BUILD_DIR="${BUILD_DIR}" BUILD_ROOT="${BUILD_ROOT}" clean build

	#import <Foundation/Foundation.h>

	// Experimental improvement to NSDictionaryOfVariableBindings where keys are simplified to remove underscores and "self." prefixes
	// so you can use the simple version within the VFL string
	//
	// Example:
	//
	// [NSLayoutConstraint constraintsWithVisualFormat:@"\|-[_foo]-[self.bar]-[baz]" options:0 metrics:nil views:NSDictionaryOfVariableBindings(_foo, self.bar, baz)];
	// -> this doesn't work, gives an error about "self."
	//