On May 13, 2010, at 11:05 AM, Michael Ash wrote:
> On Thu, May 13, 2010 at 10:56 AM, Thomas Davie wrote:
>>
>> On 13 May 2010, at 15:33, Eric Gorr wrote:
>>
>>> So long as it is ok for the string to be unique for the network the user is
>>> on only. From the docs:
>>>
>>> The ID includes the
The corner case you mention below ( [myMutableArrayInstance
isKindOfClass:[NSMutableArray class]] ) is a nonissue for a somewhat surprising
reason. All instances of NSArray are actually implemented via the concrete
class NSCFArray, which is a subclass of NSMutableArray. Thus any instances of
mu
On Tue, Jan 26, 2010 at 7:52 AM, Gustavo Pizano wrote:
>
> I duno if its the best solution but it works.. Im open to hear other
> approaches...
>
>
This isn't a threading issue, everything is happening on a single thread.
The issue is that you have a synchronous API that depends on an asynchronou
On Tue, Jun 17, 2008 at 2:42 PM, Josh de Lioncourt
<[EMAIL PROTECTED]> wrote:
>> 2. Complex keyboard control. We need to be able to intercept keystrokes,
>> be able to determine when keys are pressed or released, held in combination,
>> etc. This includes the pressing of modifier keys alone. We
>
>
> "The rich declare themselves poor,
> "And most of us are not sure,
> "If we have too much,
> "But we'll take our chances,
> "'cause God stopped keeping score."
> Praying for Time--George Michael
>
>
>
>
> On Jun 1
Performing migrations by altering the underlying structure of files you do
not understand will most likely result in data corruption. Even if the file
appears to work correctly now, that does not mean it is correct, and it does
not mean that it will continue to work in the future, especially if you
NSXMLParser needs to load everything into ram first, then it starts
generating its stream of events. I recommend filing a bug asking for
it to be enhanced to support incrementally available data. It will
definitely be a dupe (I've filed it, among others I am sure)., but the
more people who ask for
On Fri, Mar 13, 2009 at 12:04 PM, Paul Sanders wrote:
>
> (Off topic again): Call me old-fashioned, but I don't like autorelease pools
> all that much. I believe Cocoa could have gotten along just fine without
> them, had they never been invented. I prefer C++-style 'smart pointers'
> that delet
As several people have mentioned, doing this kind of thing is very skanky,
and it won't work properly under GC without some additional machinery. But
if GC is not a concern you can do something that works with a bit grotesque
monkey patching.
The below code is generic, but it mucks with everything.
On Wed, Sep 11, 2013 at 6:58 AM, Dave wrote:
>
> On 11 Sep 2013, at 05:04, Jens Alfke wrote:
>
> >
> > On Sep 10, 2013, at 12:33 PM, Dave wrote:
> >
> >> You with all this talk of memory management, you'd think that Apple (or
> someone) would have come up with a hardware solution for this by no
10 matches
Mail list logo
