9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pls. HELP porting problem
Date: Fri, 29 Apr 2005 16:38:25 +0100	[thread overview]
Message-ID: <2dfbf690b45adf596c25045a39c3cfb4@vitanuova.com> (raw)
In-Reply-To: <775b8d19050429082543bb2234@mail.gmail.com>

as i recall, this and several other peculiar effects
were the consequence of the process
by which the tree was rewritten.
it was along these lines.  (i could of course go
off and look at the source but is it worthwhile?)
you might have thought it would leave the types
alone and then when pointer-to-function appeared
as the type of an expression to which () was applied
it would insert a dereference.
but instead it applied the f to &f transformation
so *****f involved not a while loop but repeatedly
introducing &f from the bottom of the tree and having
adjacent *& cancel out (similarly, &*).  thus
	******f
	******&f
	*****f
	*****&f
	****f
	****&f
	***f
etc (i might have got the wrong number of * at some points)

little fleas indeed!



  reply	other threads:[~2005-04-29 15:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 10:53 Aharon Robbins
2005-04-29 11:59 ` Bruce Ellis
2005-04-29 15:15   ` rog
     [not found]   ` <6ea05dc57c13d1df7359ec63990a0f8b@vitanuova.com>
2005-04-29 15:25     ` Bruce Ellis
2005-04-29 15:38       ` C H Forsyth [this message]
2005-04-29 16:09         ` Bruce Ellis
2005-04-29 12:31 ` Brantley Coile
2005-04-29 18:06   ` Ah Q
2005-04-29 21:43     ` [9fans] killing none's process arisawa
2005-04-29 21:48       ` Russ Cox
2005-04-30  9:03     ` [9fans] pls. HELP porting problem Charles Forsyth
  -- strict thread matches above, loose matches on Subject: below --
2005-04-29  5:53 pac7
2005-04-29  6:01 ` boyd, rounin
2005-04-29  6:10 ` geoff
2005-04-29  8:20   ` 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=2dfbf690b45adf596c25045a39c3cfb4@vitanuova.com \
    --to=forsyth@vitanuova.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).