From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: upload / metafun
Date: Tue, 15 Dec 2020 10:35:46 +0100 [thread overview]
Message-ID: <89b8e5d8-47d0-a015-c50f-ef5a0e16a509@xs4all.nl> (raw)
Hi,
I uploaded a new lmtx. This time some work has been done at the metafun end.
At the tex end we're working on some overload protection mechanism which
involves tagging many macro so that will take a while (most tagging is
done but checking left over cases take time).
So, I wondered if we can do something similar in metapost: flag macros
and variables in order to issue a warnings when a dangerous overload
happens.
The current lmtx has this as an experiment: primitives, permanent,
immutable and mutable (so far); you can look at the *.mpxl files to get
an idea. If you say for instance
path fullcircle;
there will be a warning
metapost > overloading immutable 'fullcircle'
or when
\enabledirectives[metapost.overloadmode=error]
has been given you get an error.
The implementation is rather simple and non intrusive and differs from
the one in tex. There it is tightly integrated for all kind of reasons
(millions of macro definitions per run so efficiency matters). Also, in
metapost variables (tags) can have complex name constructions and we
only test the top level. When a overload happens (overloadmode internal
<> 0) a lua callback takes care of it.
A side effect is that we can query all hash entries and check for
consistency which is what i've done and am doing now. Of course that can
introduce issues ... just that you know.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2020-12-15 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 9:35 Hans Hagen [this message]
2020-12-15 19:09 ` RE : " Joseph
2020-12-15 19:24 ` Otared Kavian
2020-12-15 20:18 ` Pablo Rodriguez
2020-12-16 19:25 ` Hans Hagen
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=89b8e5d8-47d0-a015-c50f-ef5a0e16a509@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
/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).