From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: LuaMetaTeX code
Date: Fri, 19 Jan 2024 10:01:06 +0100 [thread overview]
Message-ID: <1fa397d4-382a-47a4-8740-db22a49517e1@xs4all.nl> (raw)
In-Reply-To: <CALJ_jGS_J9dJHZWwY5zrTJPfw2rkr6OapHJU0qmp32gyo+MVPw@mail.gmail.com>
On 1/19/2024 9:31 AM, Shiv Shankar Dayal wrote:
> I see code like
>
> # define luametatex_version 210
> # define luametatex_revision 10
> # define luametatex_release 10
> # define luametatex_version_string "2.10.10"
>
> starting with C99 these become unnecessary. Rather they should be like
> const int luametatex_version=210; const char*
> luametatex_version_string="2.10.10";
>
> These ensure type-safety in the code and are good coding practice.
Good coding practice discussions are wasted on me (you don't want me to
look at your tex code -)
The versioning is abit special in te xdue to the fact thet some numbers
en dup in registers and others as token list (string). I have considered
changing that but it would also break some 'testing for tex version' so
for now we have to accept this mix of tex/etex/pdftex inheritance.
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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-01-19 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 8:26 [NTG-context] " Shiv Shankar Dayal
2024-01-19 8:31 ` [NTG-context] " Shiv Shankar Dayal
2024-01-19 8:39 ` Taco Hoekwater
2024-01-19 8:43 ` Shiv Shankar Dayal
2024-01-19 9:01 ` Hans Hagen [this message]
2024-01-19 8:57 ` Hans Hagen
2024-01-19 9:11 ` Henri Menke via ntg-context
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=1fa397d4-382a-47a4-8740-db22a49517e1@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).