From: gdiaz@9grid.es
To: 9fans@9fans.net
Subject: Re: [9fans] naive acid debugging
Date: Wed, 15 Jul 2009 19:52:45 +0200 [thread overview]
Message-ID: <8af7d4952446de958c9dd7b977e560ab@9grid.es> (raw)
In-Reply-To: <dd6fe68a0907151130g48fcfadaq4c1a83ce8ee5aed6@mail.gmail.com>
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
next prev parent reply other threads:[~2009-07-15 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 15:26 gdiaz
2009-07-15 16:41 ` erik quanstrom
2009-07-15 18:30 ` Russ Cox
2009-07-15 17:52 ` gdiaz [this message]
2009-07-15 15:37 gdiaz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8af7d4952446de958c9dd7b977e560ab@9grid.es \
--to=gdiaz@9grid.es \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).