You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- Cool! I still think the Util above is a much more elegant solution; you can append only one string with this macro, right?typeoneerror– typeoneerror2009-07-18 13:02:46 +00:00Commented Jul 18, 2009 at 13:02
- 1True, the AS macro above does one append per line of code. If multiple appends are a common need, then more macros can be created. For example, a macro to append two strings: <pre> #define A2S(A,B,C) [[(A) stringByAppendingString:(B)] stringByAppendingString:(C)] </pre>Jim Logan– Jim Logan2009-07-18 23:54:12 +00:00Commented Jul 18, 2009 at 23:54
- 2Or, simply shorten the typing required with a macro like "#define AS stringByAppendingString", then just use "AS" where your would normally type "stringByAppendingString", and enjoy multiple appends per line of code.Jim Logan– Jim Logan2009-07-19 00:02:17 +00:00Commented Jul 19, 2009 at 0:02
- 15The problem with these macros is that they undermine one of the major goals of Objective-C, which is readability. It's extremely unclear what "AS" does. Saving a few keystrokes (most of which are handled with autocompletion) at the expense of readability is seldom a good trade-off. There are exceptions (the @"" syntax is much more readable than having to use +stringWithUTF8String: every time), but the goal should still be readability rather than simply brevity. You write once, but you debug forever.Rob Napier– Rob Napier2010-02-16 14:42:41 +00:00Commented Feb 16, 2010 at 14:42
- Hi Rob - I can't agree with you in this. Sure, "AS" is a bad name. It should be named perhaps "CAT".Fattie– Fattie2015-12-18 02:49:30 +00:00Commented Dec 18, 2015 at 2:49
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. python-3.x), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-objectivec