From: Taco Hoekwater <taco@elvenkind.com>
To: "MetaPost bug reports and discussion." <mp-implementors@tug.org>,
MetaPost List <metapost@tug.org>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Metapost beta 1.090 released
Date: Fri, 18 Jul 2008 15:10:26 +0200 [thread overview]
Message-ID: <48809642.20306@elvenkind.com> (raw)
Hi all,
I have just released the archive files for MetaPost 1.090, the
first official beta for the new stable version of MetaPost.
----------------------------------------------------------------------
What is new:
----------------------------------------------------------------------
This MetaPost release is based on MPlib. For those of you who are not
aware of the MPlib project yet:
MPlib is the name of the new, revamped version of the MetaPost
interpreter. It is implemented in Cweb, and internally consists
of a core library, an mpx generation library, and a frontend
driver program (mpost).
There are no changes to the MetaPost language, but nevertheless there
are some minor differences with the last pascal-web based version of
MetaPost (1.005):
* The MPlib distribution is released under the GPL version 2 or,
at your option, any later version.
* The commandline is slightly different, run mpost --help for details.
* The mem file format is changed, you have to regenerate any
existing ones.
* The new mpx generation library includes the label generation
functionality that was previously provided by 'makempx', and
this internal code will be used instead of an external program.
That is, unless the MPXCOMMAND variable is set in the environment
or texmf.cnf. The 'mpware' programs became obsolete and are no
longer included in the distribution.
* Most of the memory configuration variables from texmf.cnf
have become obsolete due to dynamic reallocation. The four remaining
ones are 'main_memory', 'hash_size', 'max_in_open', 'param_size'.
These are only taken into account at mem generation time, the
values are stored in and reloaded from the mem file.
* The core MPlib library does not interpret an initial '&' as anything
special and it does not support re-initialization using a different
mem file either. The command line program mpost _does_ interpret '&'
as an alias for the -mem switch to preserve (some) compatility.
* The MPlib distribution includes lua script language bindings.
----------------------------------------------------------------------
You can get the sources and a cross-compiled mingw binary for Win32
from the usual place:
http://foundry.supelec.fr/frs/?group_id=13&release_id=309
Have fun,
Taco
--
http://tug.org/metapost/
next reply other threads:[~2008-07-18 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 13:10 Taco Hoekwater [this message]
2008-07-18 18:01 ` Yue Wang
2008-07-18 18:18 ` Taco Hoekwater
2008-07-18 21:09 ` 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=48809642.20306@elvenkind.com \
--to=taco@elvenkind.com \
--cc=metapost@tug.org \
--cc=mp-implementors@tug.org \
--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).