I'm not entirely sure what the purpose of the last half of this thread
has been.
I do know that it isn't cocoa related, and has gone on long enough.
stop this thread now.
Do not start the next one.
Lest more than one player be moderated.
On 22-Mar-09, at 8:34 PM, mm w wrote:
and to close t
and to close this:
I will open the discussion: in a cpp program I will use a
type-recasting behaviour
on a circular ref ?
Cheers!
On Sun, Mar 22, 2009 at 5:26 PM, mm w wrote:
> ref my previous email,
>
> anyway there are other aspects and side effects due to the circular
> refs, and one this i
ref my previous email,
anyway there are other aspects and side effects due to the circular
refs, and one this is a memory issue, GC is now almost clever to
detect that's ObjectB reference is hold by a previous ObjectA ref to
Object0 our first reference, but it wasn't true at the beginning, and
I a
On Sun, Mar 22, 2009 at 4:32 PM, David Melgar wrote:
> Some people do that to try and impress.
> I'm not impressed.
> No useful information.
>
it's not my point, i don't understand your feeling here, I am not
trying to impress anyone, I'm only give some points
> On Mar 22, 2009, at 7:22 PM, Clar
No but this point is on left-side of this subject, anyway,
here we can see one side effect at code design-level:
here we have some symptoms:
- a lack of visibility
- when you can be the owner : "be the owner" and control what is happening
direct effect you are screwing up the garbage collection
Some people do that to try and impress.
I'm not impressed.
No useful information.
On Mar 22, 2009, at 7:22 PM, Clark Cox wrote:
It's not very conducive to conversation to make claims, and then
refuse to back them up, and leave it at "I let you discover it".
On Sun, Mar 22, 2009 at 4:19 PM, mm
It's not very conducive to conversation to make claims, and then
refuse to back them up, and leave it at "I let you discover it".
On Sun, Mar 22, 2009 at 4:19 PM, mm w wrote:
> maybe in your world, anyway there are a bunch of reasons to avoid circular
> refs
> I let you discover it
>
> Cheers!
>
maybe in your world, anyway there are a bunch of reasons to avoid circular refs
I let you discover it
Cheers!
On Sun, Mar 22, 2009 at 3:58 PM, Clark Cox wrote:
> On Sun, Mar 22, 2009 at 3:37 PM, mm w wrote:
>> Because I am like this I won't do the job for you, I will only point
>> you direction
On Sun, Mar 22, 2009 at 3:54 PM, Jean-Daniel Dupas
wrote:
>
> Le 22 mars 09 à 23:37, mm w a écrit :
>
>> Because I am like this I won't do the job for you, I will only point
>> you directions, that's it
>>
>> Google "garbage collection", it's naive to think that's a "linear" tree.
>>
>> What Bill
On Sun, Mar 22, 2009 at 3:37 PM, mm w wrote:
> Because I am like this I won't do the job for you, I will only point
> you directions, that's it
>
> Google "garbage collection", it's naive to think that's a "linear" tree.
>
> What Bill told you is right, and my comment is following his thought
>
>
Le 22 mars 09 à 23:37, mm w a écrit :
Because I am like this I won't do the job for you, I will only point
you directions, that's it
Google "garbage collection", it's naive to think that's a "linear"
tree.
What Bill told you is right, and my comment is following his thought
Avoiding circu
Because I am like this I won't do the job for you, I will only point
you directions, that's it
Google "garbage collection", it's naive to think that's a "linear" tree.
What Bill told you is right, and my comment is following his thought
Avoiding circular refs: in 95% of cases it can be avoided,
I'm confused. Bill said that the garbage collection will correctly
handle releasing these types of objects despite the circular
references. Therefore it appears that no additional actions are
required since I am using garbage collection.
What is your approach trying to solve?
I certainly do
I changed my mind, when I was writting this
- (void)sendSharedMessage:(NSString *)msg
{
NSString *print = [[[NSString alloc] initWithFormat:@" %@",msg] autorelease];
NSLog(@" %@", print);
}
anyway it doesn't change the background
On Sun, Mar 22, 2009 at 2:47 PM, mm w wrote:
> Hello Davi
Hello David,
your garbage collection approach is a bit naive, but not everything
is wrong, you can make a google search, it will point you good
resources anyway,
@implementation AppDelegate
- (void)sendSharedMessage:(NSString *)msg
{
return [[[NSString alloc] initWithFormat:@" %@",msg] autor
On Mar 21, 2009, at 9:11 PM, David wrote:
Is there any issue issuing explicit release when using garbage
collection with Leopard and Obj-c 2.0?
-release is ignored entirely.
CFRelease() work as it always does, and balances CFRetain() nicely.
But that isn't the issue.
I've become aware that
16 matches
Mail list logo
