From: "Peter A. Cejchan" <pac@next.gli.cas.cz>
To: 9fans@cse.psu.edu
Subject: [9fans] C (APE) question
Date: Mon, 13 May 2002 07:41:28 +0200 [thread overview]
Message-ID: <20020513074128.A6312@next.gli.cas.cz> (raw)
Date: 2002-05-10 06:35:06 PST
>> What is the way around calling a function w less params than declared?
>there isn't one. this is an error.
>give it all the function argument it should have.
Huh! I'll ask the original author (of the sw to be ported) to make the changes himself... Anyway, I'm happy with this, as it seems much cleaner. thanks for the help!
--
++pac.
Peter A. Cejchan
Paleobiology Lab, GLU Acad. Sci. CZ
<pac@next.gli.cas.cz>
[http | ftp]://next.gli.cas.cz
=============================================================================
The manual said: "The software needs Windows 2000 OS, or better.
So I installed Plan 9..."
=============================================================================
next reply other threads:[~2002-05-13 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 5:41 Peter A. Cejchan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 13:23 Peter A. Cejchan
2002-05-10 13:22 Russ Cox
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=20020513074128.A6312@next.gli.cas.cz \
--to=pac@next.gli.cas.cz \
--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).