From: Dekai Li <dekai@dsl.cis.upenn.edu>
To: caml-list@inria.fr
Subject: [Caml-list] How to add primitives to the standard ones?
Date: Wed, 11 Jul 2001 12:29:07 -0400 (EDT) [thread overview]
Message-ID: <Pine.SOL.4.21.0107111221250.11346-100000@codex.cis.upenn.edu> (raw)
I tried to add a primitive to the standard primitives as follows.
1. I put my foo.c file in byterun/ and put the /* ML */ at the end
of the primitives.
2. In byterun/Makefile, I added foo.o to macro OBJS and foo.c to PRIMS.
3. In stdlib/pervasives.ml, I added the declaration for my primitive and
in stdlib/pervasives.mli, I exported the primitives.
Yet it kept telling me that it can't find the external functions.
What else should I do?
Thanks.
dekai
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2001-07-11 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 16:29 Dekai Li [this message]
2001-07-12 7:45 ` Xavier Leroy
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=Pine.SOL.4.21.0107111221250.11346-100000@codex.cis.upenn.edu \
--to=dekai@dsl.cis.upenn.edu \
--cc=caml-list@inria.fr \
/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).