From: philw@plan9.att.com philw@plan9.att.com
Subject: polymorphic buglet
Date: Fri, 17 Nov 1995 09:46:46 -0500 [thread overview]
Message-ID: <19951117144646.YceAog58NUzkDPQp_Do3rnyYW2XSah6dKV8gWAtxJPw@z> (raw)
These diffs fix both of forsyth's complaints.
diff's are relative to the CD.
This fixes the poly bug.
philw-helix% diff parl.y /n/juke/plan_9/sys/src/alef/port
242,254d241
< | Ttypename
< {
< $$ = an(ONAME, nil, nil);
< if($1.t->type != TPOLY) {
< diag(nil, "type parameter must be poly [%T]", $1.t);
< $$->t = at(TPOLY, 0);
< $$->sym = enter("POLY", Ttypename);
< }
< else {
< $$->t = $1.t;
< $$->sym = $1.s;
< }
< }
This fixes the !{.
347d346
< static int itmp;
355c354
< sprint(buf, ".i%d", itmp++);
---
> sprint(buf, ".i%d", stmp++);
You need to put the !{ fix in v/reg.c, 8/reg.c and k/reg.c
I will put a boddle on the web page tonight.
phil
next reply other threads:[~1995-11-17 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-17 14:46 philw [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-11-17 9:21 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=19951117144646.YceAog58NUzkDPQp_Do3rnyYW2XSah6dKV8gWAtxJPw@z \
--to=philw@plan9.att.com \
/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).