init

On a beaglebone hardware, I want to start on a partition with a minimalist busybox system (/dev/mmcblk0p2), run some checks on the 2 other partitions (/dev/mmcblk0p5 & /dev/mmcblk0p6) containing more complete Linux systems (Angström), then start on one or the other of the 2 Linux systems based on those tests. The problem is that I cannot find how to start another system correctly from busybox. What I did: From the (perfectly working) busybox system: export PATH=/bin:/sbin:/usr/bin:/usr/sbin mount -t sysfs sysfs /sys mkdir -p /dev/pts mount -t devpts devpts /dev/pts mount /dev/mmcblk0p5 /mnt

I have generic and I want to be able to initialize it with specific constrains. The constraints are only there for initialization. The rest of the class doesn't care. Here is a simplified example: struct Generic<T> { let compare: (T, T) -> Bool init<T: Equatable>(data: [T]) { let handler: (T, T) -> Bool = { $0 == $1 } compare = handler insert(data) } init(compareHandler: (T, T) -> Bool, data[T]) { compare = self.compareHandler insert(data) } } You can see there's two initializers. The second one obviously works fine. However, in the first one the local type T is mismatched with the struct's

I'm porting some geolocation java code from http://janmatuschek.de/LatitudeLongitudeBoundingCoordinates#Java (shown below) to python. It can be initialized using two functions (fromDegrees or fromRadians). I thought I could do something like class geoLocation: _radLat = 0 _radLong = 0 _degLat = 0 _degLong = 0 def fromDegrees(lat, long): #set _radLat, _radLong, _degLat, _degLong def fromRadians(lat, long): #set _radLat, _radLong, _degLat, _degLong ... But that does not seem optimal since I set the values for _radLat, _radLong, _degLat and _degLong twice. Can I define two init functions? What's

If I have an NSObject subclass which either has no -init method or simply does nothing in -init , is there any difference between an instance created these two ways: MyClass *instance = [MyClass alloc]; MyClass *instance = [[MyClass alloc] init]; By "does nothing in -init " I mean - (id)init { self = [super init]; if (self) { } return self; } Since NSObject 's -init method itself does nothing, I can't see there being any difference, but of course the advice is that you must call -init to properly prepare an object. Here's the snippet from NSObject 's -init method which got me wondering about

I have this class: from threading import Thread import time class Timer(Thread): def __init__(self, interval, function, *args, **kwargs): Thread.__init__() self.interval = interval self.function = function self.args = args self.kwargs = kwargs self.start() def run(self): time.sleep(self.interval) return self.function(*self.args, **self.kwargs) and am calling it with this script: import timer def hello(): print \"hello, world t = timer.Timer(1.0, hello) t.run() and get this error and I can't figure out why: unbound method __init__() must be called with instance as first argument You are doing: