From: jehenrik <jehenrik@yahoo.com>
To: caml-list@inria.fr
Subject: [Caml-list] camlp4: will there be problems w/many extensions?
Date: Thu, 5 Sep 2002 12:33:13 -0400 [thread overview]
Message-ID: <2C0233FC-C0ED-11D6-9EB4-00039375801A@yahoo.com> (raw)
I am relying on a syntax for records which relies on adding six
extensions to the grammar for every new record type. Is this bad? For
now my program has only about 10 record types, but I'm worried that if
some point I start loading down the parser, I'll have to go rewrite my
macros to use a little different syntax and their own namespaces for the
record information. (And of course muck through my source code which
uses them.) Is this a useful concern? Would it be good practice to
change it anyway?
Jeff Henrikson
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
reply other threads:[~2002-09-05 16:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2C0233FC-C0ED-11D6-9EB4-00039375801A@yahoo.com \
--to=jehenrik@yahoo.com \
--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).