|
Martytoof posted:every language that isn't c-style looks weird as gently caress this x 1 million
|
# ¿ May 9, 2013 06:29 |
|
|
# ¿ May 2, 2024 21:38 |
|
Objective C
|
# ¿ May 9, 2013 22:30 |
|
it's poo poo
|
# ¿ May 10, 2013 00:11 |
|
It costs $99/year to be in the iOS developer program. The language people use to make native (ie good) apps is Objective C. You can use C# with MonoTouch if you really really really want to, but that's 3rd party. The only high level frameworks and APIs from Apple are for Objective C, with the low level stuff being in C. edit: you can download Xcode and run stuff in the iOS simulator for free, but if you wanna test on a device and publish in the App Store then you gotta pay $99/year. Doc Block fucked around with this message at 03:03 on May 11, 2013 |
# ¿ May 11, 2013 02:58 |
|
chumpchous posted:the verbosity is fine for methods and etc but it would be nice if they had some easier syntax for doing things like allocating/initializing arrays/dictionaries/etc. it seriously takes 2 lines to make an empty goddamn mutable array ??? NSMutableArray *array = [NSMutableArray array]; or, if you aren't using ARC and want an owned object returned instead of an autoreleased one: NSMutableArray *array = [[NSMutableArray alloc] init];
|
# ¿ May 12, 2013 01:26 |
|
LOL if having everything be an anonymous type is considered good code in C#. B-b-but I saved myself a split second of typing, who cares about readability! Of course, this is a Microsoft language, so of course C# devs think it's a good idea to put the class type in all methods and variable names.
|
# ¿ May 12, 2013 16:13 |
|
Mr SuperAwesome posted:neither of these things are true but please tell me more How are you not essentially putting the class type in method, property, and variable names if instead of, say, CloudSyncUpdate fileUpdate = whatever ... fileUpdate.fetchLatestUpdate() you have to do var fileUpdate = whatever ... fileUpdate.fetchLatestCloudSyncUpdate() to keep it readable? Or, so that you can still tell what fileUpdate is: var cloudSyncUpdate = whatever ... cloudSyncUpdate.fetchLatestCloudSyncUpdate() to keep it readable? Because if you're designing your API with var usage in mind, having methods just named stuff like fetchUpdate isn't very descriptive. Disclaimer: I've only dabbled with C#, and it was a long time ago. Doc Block fucked around with this message at 16:56 on May 12, 2013 |
# ¿ May 12, 2013 16:42 |
|
That is the One True Brace Style. Functions & methods get the opening brace on a separate line. if/else, for loops, etc., get the opening brace on the same line. The closing brace always goes on a separate line.
|
# ¿ May 16, 2013 02:01 |
|
Shaggar posted:yes the one truly bad brace style And what, pray tell, is the Shaggar-approved brace style?
|
# ¿ May 16, 2013 02:48 |
|
lol you would know
|
# ¿ May 16, 2013 03:20 |
|
Nomnom Cookie posted:my shaggier.xls has allman on it. if thats the one where opening braces always go on the same line then hes right allman style is this dumbass poo poo code:
code:
|
# ¿ May 16, 2013 04:04 |
|
When I was only three My momma said to me "Don't go hanging with the web devs Or you're gonna learn PHP"
|
# ¿ May 16, 2013 11:56 |
|
Also, tabs are 4 spaces, saved as hard tabs. 8 spaces is acceptable, depending on the language.
|
# ¿ May 16, 2013 14:55 |
|
Tiny Bug Child posted:this is almost correct, but opening braces never go on their own line Maybe if you're writing in a babby p language, but in Real Programming Languages, when writing functions & methods the opening brace goes on its own line.
|
# ¿ May 16, 2013 16:43 |
|
I'm the one line case statements.
|
# ¿ May 17, 2013 05:25 |
|
lol
|
# ¿ May 18, 2013 18:30 |
|
Don't use global variables, problem solved.
|
# ¿ May 19, 2013 07:04 |
|
LOL wrong
|
# ¿ May 19, 2013 14:42 |
|
Ericadia posted:Yeah I think it looks better this way tbh. When I see braces I think multiple statements. What happens when you add a statement but forget to add the braces?
|
# ¿ May 19, 2013 19:06 |
|
The worst programmers are the ones who can't/won't read compiler error messages, and instead immediately jump on [whatever programmer forum/site] and ask people how to fix it. Especially when they just paraphrase the error message instead of posting it and the offending code. Especially especially when they're using clang.
|
# ¿ May 20, 2013 16:07 |
|
Yeah, umm, gently caress that poo poo.
|
# ¿ May 24, 2013 03:35 |
|
chumpchous posted:every time i get probated (a lot), i secretly feel kinda bad about it (once or twice ifelt really bad because i definitely deserved it). if anyone ever commented on or cared about it i think it would suck a lot more than i'd ever admit you were pretty much asking for it with the maggots in noses videos you linked to.
|
# ¿ May 29, 2013 09:00 |
|
Shaggar posted:none of this has 2 do w/ ios. LOL if ur a developer but aren't making mobile apps ITYOOL 2013
|
# ¿ May 31, 2013 00:00 |
|
b-b-but the Ruby guys said Xcode is bad and that I should use Vim!
|
# ¿ May 31, 2013 03:03 |
|
THC posted:Im inclined to think the entire message passing concept is apple being different for the sake of being different. (NB: I realize this is not the actual reason why obj-c has messaging but to someone raised on c/++ c# and java it is just so very peculiar.) they just get turned into function calls at compile time anyway so wtf No they don't, at least not in the way that you mean. They get turned into calls to the C function objc_msgSend(), which sends the object the message. The message passing is what makes Objective-C such a dynamic language. For instance, you can add methods to objects at runtime because calling methods is really just sending messages instead of making direct function calls like in c++/c#/whatever. And you can ask an object if it responds to a given message so that you can, say, use a method added in a certain version of iOS but still maintain backward compatibility without having to remember what specific version of iOS it was that added the method. You can forward messages to other objects, or even make an object that consumes all messages. Message passing is one of the things that I like about Objective-C. Doc Block fucked around with this message at 09:12 on May 31, 2013 |
# ¿ May 31, 2013 09:09 |
|
prefect posted:is this a religious thing, or was there some guy named church who thought them up? I think he means Roman Numerals
|
# ¿ Jun 9, 2013 23:34 |
|
Jerry SanDisky posted:Lots, usually on the same monitor
|
# ¿ Jun 10, 2013 07:13 |
|
THC posted:in obj-C is there any particular reason to use your own instance variables and methods instead of just dropping a @property in there? they're not doing anything fancy with the accessors except return some value so im confused why they dont just use @properties. Property setters are slower because they also have to do all the KVO stuff and whatnot. ARC has pretty much eliminated the reason people started using properties for instance variables.
|
# ¿ Jun 17, 2013 20:11 |
|
Brain Candy posted:most people are assholes. all people are terrible.
|
# ¿ Jun 18, 2013 22:46 |
|
uG posted:visual C will never be updated past c89 so we can deduce that c99 is not real C msvc is poo poo. ms going out of their way to purposefully not implement c99 is bullshit. making their own c99-esque safe string functions that take the exact same arguments and produce the same results but have different names is bullshit. clang/LLVM supremacy.
|
# ¿ Jun 21, 2013 20:18 |
|
Why learn Ruby when you can learn Objective-C, which is rapidly being turned into compiled Ruby by all the Ruby devs flocking to it.
|
# ¿ Jun 22, 2013 00:06 |
|
chumpchous posted:objective c is a really stupid language seriously use ruby motion and if you need something to be fast write it in c said a terrible programmer. polpotpi posted:theres no good tutorials or books for objective c "how do i maek iphone apps, post tutorials plz."
|
# ¿ Jun 22, 2013 00:33 |
|
Bloody posted:why not gcc/g++? because it's poo poo. it's slower, its c++11 implementation isn't as complete as clang's, and it produces really awful error messages. clang is fast. clang has a (nearly) complete c++11 implementation, and, thanks to its developers trying to make it understand your code really well, it produces error messages that are so helpful it can actually suggest fixes. that same code understanding also gives clang a really good static analyzer and makes things like Objective-C's ARC possible. additionally, clang/LLVM are architecturally superior to GCC. GCC is basically a big monolithic thing that its devs are only now trying to modularize in any meaningful way. LLVM is constructed as a bunch of independent libraries, and these libraries can be used by other, non-LLVM code. you can use this to build LLVM right into an IDE like Xcode does, or use it to build your own code analysis tools, or use it to more easily create your own domain-specific language. you can even write your own optimization steps.
|
# ¿ Jun 22, 2013 02:35 |
|
uG posted:if you need to be coddled through your mistakes then sure thats p cool what's cool is that clang/LLVM is better than GCC at analyzing your code. on the surface this manifests as more helpful error messages, it also leads to more optimization opportunities and better code analysis tools. also, final decisions re: clang/LLVM don't rest with a bunch of freetards.
|
# ¿ Jun 22, 2013 05:21 |
|
If you learn Objective-C from a book be prepared to do a substantial amount of catch-up reading on line.
|
# ¿ Jun 22, 2013 17:29 |
|
OBAMA BIN LinkedIn posted:just use mvim idiots ftfy, because if u don't use mac
|
# ¿ Jun 24, 2013 07:33 |
|
Use BBEdit (or TextWrangler if you're a rule 36er) for editing text and writing dumb p-lang poo poo.
|
# ¿ Jun 24, 2013 16:31 |
|
BONGHITZ posted:textwrangler Nope, TextWrangler is a perfectly good text editor if you're somehow a Rule 36er (the non-poor best text editor is BBEdit, the paid version of TextWrangler)
|
# ¿ Jun 28, 2013 00:54 |
|
hey guys this honorary p-lang is better than that actual p-lang!
|
# ¿ Jun 28, 2013 02:22 |
|
|
# ¿ May 2, 2024 21:38 |
|
what moobie is dat?
|
# ¿ Jun 28, 2013 19:10 |