Re: upload / metafun

[Otared Kavian <otared@gmail.com>]

Hi Hans,

Thanks for the new upload. 
With your comments, I understand that, following the discussion with Aditya, when using the new version I should not define in Metafun a new function named
	dotlabel
in order to have a square dot… Actually I called it mydotlabel in order to be able to change the shape of the dot, so I will be on the safe side when I can download the new version.

However after running install. sh on MacOS, I still get current version: 2020.12.10 22:26, even after removing the .tma files.
So I guess I have to wait a little bit for the new version to be upoaded.

Best regards: Otared



> On 15 Dec 2020, at 10:35, Hans Hagen <j.hagen@xs4all.nl> wrote:
> 
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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
___________________________________________________________________________________