From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Good enough approximation for ape/pcc
Date: Sun, 9 Apr 2006 17:57:08 -0400 [thread overview]
Date: Sun, 09 Apr 2006 17:57:08 -0400 [thread overview]
Message-ID: <20060409215708.12577.qmail@g.galapagos.bx.psu.edu> (raw)
In-Reply-To: <e745ca9693060328854df344c855c84c@swtch.com>
| if you're writing the print statement,
| you *know* which function you're in.
But why should I have to type the particular value several times?
What if I change the name of the function later? Isn't that what
variables are for?
| it's only useful inside macros,
| which are mostly deprecated.
Nah, even simple function calls can use it.
check(a, b, c, __func__);
It's true, it would be nice to find out the caller from within check(),
but this achieves most of the utility with a much simpler implementation.
next prev parent reply other threads:[~2006-04-09 21:57 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 18:13 Fernan Bolando
2006-04-07 19:43 ` Russ Cox
2006-04-07 19:01 ` Fernan Bolando
2006-04-07 19:17 ` uriel
2006-04-07 19:57 ` David Leimbach
2006-04-07 21:52 ` Russ Cox
2006-04-07 21:07 ` David Leimbach
2006-04-08 22:39 ` Lluís Batlle i Rossell
2006-04-08 23:50 ` quanstro
2006-04-09 0:05 ` Russ Cox
2006-04-09 5:55 ` Scott Schwartz
2006-04-09 16:56 ` Russ Cox
2006-04-09 21:57 ` Scott Schwartz [this message]
2006-04-09 23:04 ` Russ Cox
2006-04-10 2:49 ` Scott Schwartz
2006-04-10 4:19 ` Russ Cox
2006-04-10 4:03 ` lucio
2006-04-10 8:37 ` Bruce Ellis
2006-04-10 14:42 ` Paul Lalonde
2006-04-10 11:11 ` quanstro
2006-04-10 11:34 ` Brantley Coile
2006-04-10 14:09 ` Ronald G Minnich
2006-04-10 14:49 ` Paul Lalonde
2006-04-10 15:26 ` andrey mirtchovski
2006-04-10 22:07 ` Andrew Simmons
2006-04-10 23:04 ` Andy Newman
2006-04-10 23:18 ` David Leimbach
2006-04-10 23:51 ` Roman Shaposhnick
2006-04-11 0:07 ` David Leimbach
[not found] ` <3e1162e60604101707v6214a809h516a223bf5d14a06@mail.gmail.co m>
2006-04-11 1:26 ` Andrew Simmons
2006-04-11 2:37 ` quanstro
2006-04-11 4:20 ` Bruce Ellis
2006-04-11 5:40 ` Skip Tavakkolian
2006-04-11 8:18 ` Bruce Ellis
2006-04-11 8:56 ` Charles Forsyth
2006-04-11 9:00 ` Bruce Ellis
2006-04-11 8:17 ` Lluís Batlle
2006-04-11 21:30 ` Roman Shaposhnick
2006-04-11 22:37 ` Russ Cox
2006-04-11 22:05 ` Roman Shaposhnick
2006-04-11 21:25 ` Roman Shaposhnick
2006-04-10 9:57 ` Charles Forsyth
2006-04-09 23:32 ` geoff
2006-04-07 20:10 ` Russ Cox
[not found] ` <ba5b34e5051e1f0238a2df3f641d4598@cat-v.org>
2006-04-08 4:18 ` Fernan Bolando
2006-04-08 5:24 ` Russ Cox
2006-04-08 7:28 ` Bruce Ellis
2006-04-08 16:18 ` Rob Pike
2006-04-08 16:42 ` Bruce Ellis
2006-04-09 23:04 erik quanstrom
2006-04-10 23:51 erik quanstrom
2006-04-10 23:53 erik quanstrom
2006-04-11 0:37 erik quanstrom
2006-04-11 0:40 erik quanstrom
2006-04-11 10:18 Andrew Simmons
2006-04-11 10:55 ` Brantley Coile
2006-04-11 11:25 ` quanstro
2006-04-11 12:58 Russ Cox
2006-04-12 0:50 erik quanstrom
2006-04-12 1:09 ` Charles Forsyth
2006-04-12 11:18 ` Aharon Robbins
2006-04-12 11:31 ` R
2006-04-12 14:01 ` Russ Cox
2006-04-12 13:44 ` Charles Forsyth
2006-04-12 14:50 ` Brantley Coile
2006-04-12 1:15 erik quanstrom
2006-04-12 1:23 ` Charles Forsyth
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=20060409215708.12577.qmail@g.galapagos.bx.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--cc=9fans@cse.psu.edu \
/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).