9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mallocz in APE
Date: Thu, 18 Jul 2013 17:12:58 +0200	[thread overview]
Message-ID: <20130718151258.GA5201@polynum.com> (raw)
In-Reply-To: <f346f3d4e29d7ca9be65bf45446ed6bf@quintile.net>

On Thu, Jul 18, 2013 at 03:48:17PM +0100, Steve Simon wrote:
>
> 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.

No, you are perfectly right. Having to deal with "porting" a software
to various OSes, every namespace pollution comes in the way because
one can not rely on one and only one doc: precisely the standard,
without having to know the various time dependent idiosynchrazies
(the standard says that it is that, and everything else should not
be here except with a leading '_' etc.).  (I had to add macros for
several TeX routines whose names are not conflicting with ANSI C,
but happen to conflict with routines added by system X in its libc;
and generally, one add a macro definition to rename... before being
told that the new name is conflicting with a name added by system
Y version a.b.c.d in its libc...; so the "solution" is always a
temporary one; with the standard, one could prove being right;
without the standard, one can only prove being OK "so far"...)

--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  reply	other threads:[~2013-07-18 15:12 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
2013-07-18 15:12       ` tlaronde [this message]
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=20130718151258.GA5201@polynum.com \
    --to=tlaronde@polynum.com \
    --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).