From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@9fans.net
Date: Wed, 15 Jul 2009 19:52:45 +0200
From: gdiaz@9grid.es
Message-ID: <8af7d4952446de958c9dd7b977e560ab@9grid.es>
In-Reply-To: <dd6fe68a0907151130g48fcfadaq4c1a83ce8ee5aed6@mail.gmail.com>
References: <73875a2249f78ec9cd60d0ef39b5f9e6@9grid.es>
	<588ebae7237a9a5546342bea3d5c89eb@coraid.com>
	<dd6fe68a0907151130g48fcfadaq4c1a83ce8ee5aed6@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [9fans] naive acid debugging
Topicbox-Message-UUID: 218a24ca-ead5-11e9-9d60-3106f5b1d025

Hello

Thanks Russ, seems that even though i tried to use your iwp9 2007 talk as a reference, i missed the point, i should read more carefully.

gabi

>>>               print("f->mb=", f->mb\X,"       =?      mb=",mb\X,"\n");
>>>               f=f->next;
>
> Always use . (never ->) in acid.
>
> If f is a pointer, then the acid expression f.mb
> is like the C expression (*f).mb aka f->mb.
> The acid expression f->mb is like the C expression (**f).mb.
> By using -> here you are indirecting one level too far.
>
> -> is one of those acid features that seems
> to exist only to cause confusion.
>
> Russ