g type of exception, it fails very early in the stack unwinding so
that I have a good idea of where the problem is.
On Jun 28, 2009, at 7:23 PM, Chris Idou wrote:
____
From: James Gregurich
3) I don't allow exceptions of any kind to propagate int
:mFailedLogPathSPtr.get() atomically:YES];
OBJC_EXCEPTION_CATCH
}
On Jun 27, 2009, at 4:39 PM, Greg Guerin wrote:
James Gregurich wrote:
1) I have convenience macros that @catch and throw NSExceptions for
the legacy 32 bit environment. I don't allow legacy objc exceptions
to
Bill,
If you guys are going to some day make that statement the law, then
please keep in mind that whatever you do has to operate with cross
platform C++ code using standard memory management techniques. Many of
us have to deal with other unix systems and Windows. We need this
stuff to a
1) I have convenience macros that @catch and throw NSExceptions for
the legacy 32 bit environment. I don't allow legacy objc exceptions to
propagate out of code blocks.
2) I don't use @synchronize. I use boost::thread::mutex so that I have
one consistent, standard locking API throughout
7;t useful.
my statement is that I'd rather use shared_ptr & weak_ptr. I'll know exactly
what my system is doing in a way that is as predictable as possible yet is
completely safe and reliableand maintainable.
On Friday, June 26, 2009, at 06:56PM, "Michael Ash"
On Friday, June 26, 2009, at 06:39PM, "Kyle Sluder"
wrote:
>On Fri, Jun 26, 2009 at 6:21 PM, James Gregurich wrote:
>>>That wasn't where I was going with that. I was making two distinct
>>>points: 1) You can't depend on any Cocoa object actually
much better response. thanks.
The sarcastic stuff gets old.
On Friday, June 26, 2009, at 05:54PM, "Kyle Sluder"
wrote:
>That wasn't where I was going with that. I was making two distinct
>points: 1) You can't depend on any Cocoa object actually getting
>released at any time.
I certainly
gs who have the patience to sit
around arguing over the obvious.
I know exactly what I want and why I want it. you do whatever floats your boat.
I'll do what floats mine.
On Friday, June 26, 2009, at 05:26PM, "Andy Lee" wrote:
>On Friday, June 26, 2009, at 07:27PM, "James
On Friday, June 26, 2009, at 04:41PM, "Kyle Sluder"
wrote:
>100% might. Maybe 0% today, and then tomorrow Apple might release an
>update that causes all objects to hang around forever. You don't
>know, and you shouldn't care.
I don't. in practice its not particularly relevant as I can't thi
s of
manual memory management in objcI'd buy that statement if it was made.
On Friday, June 26, 2009, at 02:52PM, "Michael Ash"
wrote:
>On Fri, Jun 26, 2009 at 2:31 PM, James Gregurich wrote:
>>
>> If my resource is handed off to some external subsystem for
eally straightforward to use common header files with OS-specific
implementations.
yea...yea...yea...you Apple employees don't have to worry about Windows, but
I'm not that fortunate. :)
On Friday, June 26, 2009, at 12:08PM, "Bill Bumgarner" wrote:
>On Jun 26, 200
as to publish a solution I
found useful. One is free to use it or ignore it.
On Thursday, June 25, 2009, at 11:39PM, "Chris Idou" wrote:
>
>
>
>____
>From: James Gregurich
>
>> I have read up on GC, and I don't like the idea of int
te. If the value is in an
invalid state, an exception is thrown and everything cleanly unwinds
and the system can react and cleanly recover.
On Jun 25, 2009, at 10:13 PM, Stephen J. Butler wrote:
On Fri, Jun 26, 2009 at 12:06 AM, James Gregurich> wrote:
I also take advantage of referen
I'll speak up and throw a wrinkle into this discussion. I found it
useful and may some others will also.
I have read up on GC, and I don't like the idea of introducing non-
deterministic behavior into my code base. However, it is true that
manually retaining and releasing pointers is inher
:] and pass that fetch request to
[NSFetchedPropertyDescription setFetchRequest:]? I would assume in my
example that my destination entity is the story.
-James Gregurich
Engineering Manager
Markzware
On Aug 3, 2008, at 10:37 AM, Omar Qazi wrote:
Create an NSFetechedPropertyDescription by
apId has a 1-1 relationship with map.mapId
map.storyId has a 1-many relationship with story.storyId2
What is the correct way to programmatically add a fetched property to
the box to get the list of stories for a given box managed object?
thanks,
James Gregurich
Engineering Manager
Markz
greetings.
Markzware is in need of a WWDC ticket. If anyone wants to sell one, please
contact me at [EMAIL PROTECTED] The sellout caught us by surprise.
thanks,
James Gregurich
Engineering Manager
Markzware
___
Cocoa-dev mailing list (Cocoa-dev
17 matches
Mail list logo
