(This started out as a comment to
(e:jenks) comment on
(e:paul) 's journal, but I think it's gotten too long for a comment. )
I'll be getting an iPhone from work, hopefully, that we'll try to use with the ERP system we're developing.
We're kinda bummed that we can't take the OS X code that we're using in our database client and reuse it to make a stripped-down version that runs on the iPhone. And I'm personally bummed that there's not going to be, at least for a while, an iPhone Cocoa API that would vastly increase the potential job opportunies for myself (and
(e:zobar) as well). So much for my fantasies of buying a house on Richmond with plenty of insulation, no dust, and central air.
Yes, it sucks, but then again, Cingular has been very good about respecting users' ability to use bluetooth and the users own file's however they see fit. Someone like T-Mobile or Verizon or Sprint deciding that I can't put a public-domain midi file on my phone as a ringtone and charging me $$$ to have to use their ringtone from their network, which I'll have to keep paying for over and over again when my subscription to ringtone runs out, pisses me off vastly more than the iPhone apps issue.
I've heard that one of the reasons why Apple went with Cingular (aka AT&T) only is that they were given a wide amount of latitude in what they are allowed to do. If Verizon or T-mobile had iPhones, they would probably put in enough restrictions that sucked even more than Apple's.
Here is the updated manual on Object Orientation in PHP as of version 5 :::link:::
Holy crap (e:zobar), why on earth would you base your API on PHP 4.4. No one is going to use a PHP 4 based API very much longer. Your problem had to do with a fatal flaw in pre-php 5 that resulted in the developer needing to explicitly call objects by reference.
All of the object orientation in PHP was completely rewritten after version 5 and is much more on par with other languages - it makes no sense to use version 4.4. You are also missing out on public, private, protected, __get, __set, __call, __construct, __destruct, __wake, __sleep, normal inheritance, passing by reference, argument typing and so much more. Why don't you just go back to OS 8 while you are at it, lol.
I mean PHP 5 addressed these issues but by basing your API a non-current or even close to current version of an open-source project, how can you expect it to be great.
Yeah, so much open source software is crap from a usability standpoint. I'm doing a project right now in PHP. You'd think that with so many people using and developing PHP, it would have been pretty mature by version 4.4. It ain't.* To whit: I have some code that puts together a fairly complex object-oriented data structure.
Works:
$template = &new KTDocument('skins/default/base');
Fails in bizarre and subtle ways:
$template = new KTDocument('skins/default/base');
It took me hours to figure that out. If I, the developer, can't get it right, how can I expect other clients of my API to figure it out?
- Z
_______________