9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] python won't link with type safe linker, i.e. -T
Date: Wed, 17 Jan 2007 09:00:28 -0700	[thread overview]
Message-ID: <13426df10701170800r355135c6md0190e783704fc47@mail.gmail.com> (raw)

they do things like this:

foo.h:
struct x {
#ifdef ZARDOZ
int i;
#endif
int j;
};

provider.c:
int somefunc(struct x *x){
  x->j = 1;
}
a.c:
#include foo.h

struct x x;
somefunc(&x);

b.c
#define ZARDOZ
#include a.c


Yes, include a.c. I kid you not. So the type signature of the function
somefunc is different in a and b. This will all "work", with -T turned
off, but it's too clever for me.

We go for simpler things here in NM, such as a  school down south
that, having had a principal dismissed on drug charges, and gang
fights, and sundry other problems, decided to hire an image
consultant, to provide the school with a logo, a standard presentation
style for their powerpont talks, rules for usage of the logo, and a
set of other tools to help improve the school's brand recognition.
Oops, I digressed. But NM is interesting, is it not? Our own Lottery
Authority hired a lobbyist, to ensure that our legislature not enact
rules requiring that Lottery money go to schools instead of Lottery
Authority staff. Lobbyist paid for by our Lottery Authority, a part of
the same government that controls its budget, so is this re-entrancy
in government?  ... Oops, I digressed.

Working through it now .... twisty ... little ... maze. .......

ron


             reply	other threads:[~2007-01-17 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17 16:00 ron minnich [this message]
2007-01-17 17:20 ` Skip Tavakkolian

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=13426df10701170800r355135c6md0190e783704fc47@mail.gmail.com \
    --to=rminnich@gmail.com \
    --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).