9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] mallocz in APE
Date: Thu, 18 Jul 2013 15:48:17 +0100	[thread overview]
Message-ID: <f346f3d4e29d7ca9be65bf45446ed6bf@quintile.net> (raw)
In-Reply-To: <CAG3N4d-x5ONcuMq7j+x3TrwkvNpH0acUHK_urZhrdSCS=0_Gag@mail.gmail.com>

>> Having said this what about setmalloctag() getcallerpc(), etc etc.
>
>It is internal to the libraries and is not exposed to the APE apps, right?

But because getcallerpc() is not prefexid by an underscore or file scope,
by the "rules" it is poluting the namespace of the APE app.

Its a minor thing I know but somone put a lot of effort into adding _MALLOCZ() and
all the other internal funcs it seems a pity to not do the same with
setmalloctag() and getcallerpc().

its not a major issue, probably OCD on my part.

-Steve



  reply	other threads:[~2013-07-18 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18  8:49 yaroslav
2013-07-18 10:45 ` Steve Simon
2013-07-18 14:30   ` Yaroslav
2013-07-18 14:48     ` Steve Simon [this message]
2013-07-18 15:12       ` tlaronde
2013-07-18 15:21       ` erik quanstrom

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=f346f3d4e29d7ca9be65bf45446ed6bf@quintile.net \
    --to=steve@quintile.net \
    --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).