> On 21 juil. 2013, at 17:04, "Eric E. Dolecki" wrote:
>
> Outside of doing that, I'm not sure why things would be down for such an
> extended period of time.
The fact that the main page is still accessible means the server did not crash.
Could be the database with all developers ID, profiles…
Kyle,
> Following that line of thought, how many of you actually think griping
> on this list is going to accomplish anything other than filling up
> everyone else's inboxes from what would otherwise be one of the
> remaining useful channels?
While I agree with you, I think it is also essential t
Hi everybody,
I have a very simple question: if I embed a C-function (more precisely, a
callback from an external C-library) in an Obj-C object, can I expect this
function to behave like a regular method? I.e. can it freely access ‘self’ and
other attributes?
Thanks a lot!
Vincent
Rick,
thanks for answering, because what I found on the Internet seems contradictory.
Some say that if the C function is placed inside the implementation block, then
it can access attributes as if it were a true Obj-C method; some say otherwise.
So it’s a bit difficult to find a definitive answ
Hi and thanks a lot to anybody!
I posted some answer before, but since it included a screenshot I’m afraid it
didn’t make it through. I was just trying to show that when I access an iVar of
‘self’ in the C-function (e.g. self -> _egg), Xcode autocompletion pop-up shows
the iVars list, but each
Folks,
I apologize if this question looks stupid or contrived. Here it is: is it
permissible to use [@“” mutableCopy] to initialize (or reset) a NSMutableString
instead of the more classical [[NSMutableString alloc] init]?
Thanks a lot!
Vincent
___
Le 31 juil. 2013 à 20:15, Mike Abdullah a écrit :
>> I apologize if this question looks stupid or contrived. Here it is: is it
>> permissible to use [@“” mutableCopy] to initialize (or reset) a
>> NSMutableString instead of the more classical [[NSMutableString alloc] init]?
>
> Yes.
Thanks!
Thanks to all for answering,
> Why would there be? Your just asking for a mutable copy of an empty string.
> It should be equivalent to [[NSMutableString alloc] initWithString:@« »]
But much slower I expect, since it creates a NSString, takes a mutable copy,
then implicitly releases the consta
Greg,
thanks for diverting some of your time testing this. As someone already
commented, the results are somehow consistent with “common sense”, whatever
that means (cf. below).
> ARC and non-ARC scores are the same within measurement noise, except for
> [NSMutableString string] where ARC can
Le 31 juil. 2013 à 22:38, Greg Parker a écrit :
> Not necessarily. If you have long string and you want to clear it and re-fill
> it with another long string, then it may be faster to use
> -deleteCharactersInRange: in order to avoid memory re-allocation overhead.
> But that possibility depend
Mostly, this is not going to change anything. You will see your code size
increase, because unless you use PIC, you’ll have to store 64-bit addresses
instead of 32. There will be more cache misses as your memory space becomes
sparse. It will surely run faster, but not because the bus size has be
> Thanks for this remainder, but I think we all already know that 620k is
> enough for anyone…
Frankly, Jean-Daniel, I don’t want to get involved in a pointless bickering,
but all I need on a phone was almost already running twenty-five years ago on
my first Atari 520ST with, yes, 512 KiB of RA
Scott,
> No, but it's great to device to access data, perhaps even bits pulled out
> from a huge pile, and preferably pulled out extremely quickly.
> And, anyway, why shouldn't it be a huge database machine???
I meant, it is not designed to serve as a database machine. I can’t possibly
imagine
301 - 313 of 313 matches
Mail list logo
