Hi Jens,
Thanks again for your reply. I'm sure this has been done to death over the
years on the list, but... you would definitely recommend ARC then, would you?
I've been a bit put off by what seems like regular questions on the list(s)
about debugging and fixing edge cases where ARC doesn't w
I can’t imagine going back to manual retain release. ARC lifted hours of work
away from writing code because you just use objects and they stay when they
need to stay go away when you’re done with them. I see hardly any questions
about ARC at all, there were some at the very start, but they pete
Hi, all.
My question is about the convention of the standard namespace in C++. firstly,
let's read the following classic example in C/C++:
,-
| #include
| #include
|
| double fabs(double a)
| {
| return -1.0*a;
| }
|
| int main()
| {
| double b=fabs(3.0);
|
> On May 12, 2016, at 7:00 AM, 军其 胡 wrote:
> Hi, all.
>
> My question is about the convention of the standard namespace in C++.
> firstly, let's read the following classic example in C/C++:
>
> ,-
> | #include
> | #include
> |
> | double fabs(double a)
> | {
> |
> On May 12, 2016, at 1:16 AM, Jonathan Taylor
> wrote:
>
> you would definitely recommend ARC then, would you?
Totally. As Roland said, I would never go back.
> I've been a bit put off by what seems like regular questions on the list(s)
> about debugging and fixing edge cases where ARC does
I’m making more use of unwind segues to try and get to the point I have ‘go
forward’ and ‘go backward’ code in one place in the same class. So during
prepareForSegue I set some stuff up, during my unwind segue method I tear it
down again. Don’t use it for everything, but for some complex present
