9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] what is this, pls?
Date: Wed,  5 Jun 2002 11:38:19 +0100	[thread overview]
Message-ID: <21dd4989413ede4680b85a715d441560@caldo.demon.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 382 bytes --]

the compilers were built using a lazy compiler construction algorithm
in which operators were added as required by the system, and
they don't currently provide full support for all 64 bit (vlong)
operations.

since Dir.length and a few other system values are now 64 bit,
i can see it being changed eventually.

meanwhile, you need to rewrite the ?: using an if statement.

[-- Attachment #2: Type: message/rfc822, Size: 2427 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 232 bytes --]

Can somebody show me a way around this? (whole ssi.c is at http://next.gli.cas.cz/ssi.c, if needed).
TIA,
--
++pac.

Peter A. Cejchan
Paleobiology Lab, GLU Acad. Sci. CZ
<pac@next.gli.cas.cz>
[http | ftp]://next.gli.cas.cz

[-- Attachment #2.1.2: WHATISTHIS --]
[-- Type: text/plain, Size: 216 bytes --]

pcc -c -B -DHAVE_CONFIG_H -D_POSIX_SOURCE -D_BSD_EXTENSION ssi.c
/usr/pac/wrk/infernal-0.1/squid/ssi.c:745[stdin:4020] unknown vlong LIST
/usr/pac/wrk/infernal-0.1/squid/ssi.c:745[stdin:4020] unknown vlong COND


[-- Attachment #2.1.3: CODE --]
[-- Type: text/plain, Size: 158 bytes --]

 fprintf(g->ptmp, "%s\t%d\t%llu\t%llu\t%lu\n", \
	      key, fh, r_off->off.i64, \
	      d_off == NULL? 0 : d_off->off.i64, \
	      (unsigned long) L);

             reply	other threads:[~2002-06-05 10:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05 10:38 forsyth [this message]
2002-06-10 10:03 ` peter a. cejchan
2002-06-05 10:42 Peter A. Cejchan

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=21dd4989413ede4680b85a715d441560@caldo.demon.co.uk \
    --to=forsyth@caldo.demon.co.uk \
    --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).