canvas.drawImage(kittens.subImage(vec2(10,10),vec2(20,20)),vec2(30,30))
vs [canvas drawImage:[kittens subImageAt:vec2(10,10) withSize:vec2(20,20)] at:vec2(30,30)] #define withZip someoneCouldntComeUpWithAShorterNameWithZipcode
#define dictWith dictionaryWithObjectsAndKeys
or
#define dictWith NSDictionary dictionaryWithObjectsAndKeys
so you can [dictWith: key, value, key, value]
:) I forget, does XCode intelligently handle macros? Or does using a macro destroy its helpful features, like code completion?I actually have a "hashWith" utility function for my .NET code. Saves me a ton of ugh-induced headaches.
Instead of using a macro for the selector:
NSDictionary *frob = [NSDictionary macroHere:v1, k1, v0, k0, nil];
It would probably be far more efficient to macro the entire call using C99's variadics: NSDictionary *frob = DICT(v1, k1, v0, k0);
Still wouldn't walk that road, personally.IMO, something like `[NSDictionary with:key,val,key,val,nil]` is far less brain-taxing than `DICT(key,val,key,val)`. It fits without modifying the language or the syntax, it merely makes something long shorter, and the usage implies it does nothing "shiny" - you even keep the class name you're calling, making it clearer what you should be expecting, and it still allows access to all other parameters without modification or even thinking differently. DICT(...) is ambiguous about what kind of dictionary it's returning.
I wasn't too happy about that :/
Dude. Are you still using CGA? Unless for your IDE you're running emacs on your wristwatch or phone there's no place for that shit in the real world, and you have no excuse.
Ditch that green cathode ray tube, here, have 50c and go buy yourself a real monitor. :D
This is Guido's reasoning for keeping PEP8's rule to 80 chars.
To add maiming to injury, these guys write in modern Cobol (a.k.a Java).
Not to mention that they can't print the code -- since it is 150+ chars wide(!) -- and browse it at a cafe. (I love my iPad, but It'll be iPad 3 before it is half as nice for browsing code [edit: as paper].)
I have about 2 full pages of code on the same size of monitor. Of scripting language. I doubt that I have abnormally bad memory or write too complex code... I just like to be productive.
Edit: oK, downvote if you want. But please also add a counter argument for wasting all that screen area?
You can't print code longer than 150 characters wide?
Since when?
The point of printing and browsing code is that it is easier and nicer than to read it on a screen (you'll have a portable with you at the cafe anyway to search, annotate, etc.) If you get lots of broken lines, it isn't readable.
Point was, you lose a capability with long lines -- a nice way to go over code. This is important for many of us.
Edit: Point jedsmith, write it off as grumpy-old-man syndrome. Sigh, I just can't get that this isn't understood by everyone, anymore.
We no longer live in the days of typewriters or daisychain printers with fixed column widths.
We now have these wonderful things called laser printers which can print using fonts.
Fonts are resizeable. Even to the point that 150+ columns could be fit on one unbroken line.
And even lines that long can be quite readable if you print in landscape.
Second, in what you quote from: easier and nicer than to read it on a screen.
So your argument seems to be that it is equally nice to read fewer lines of paper in a smaller font. Huh? Also, my eyes can't handle 4 pages on a page any more -- and your eyes won't be able to do that after 40, either.