ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Shiv Shankar Dayal <shivshankar.dayal@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: LuaMetaTeX code
Date: Fri, 19 Jan 2024 14:01:31 +0530	[thread overview]
Message-ID: <CALJ_jGS_J9dJHZWwY5zrTJPfw2rkr6OapHJU0qmp32gyo+MVPw@mail.gmail.com> (raw)
In-Reply-To: <CALJ_jGQg-Xu2hXNiFpExCMQt-KUXGUMrcajEZJ_ssBLr7Yw7uw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1014 bytes --]

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.

On Fri, Jan 19, 2024 at 1:56 PM Shiv Shankar Dayal <
shivshankar.dayal@gmail.com> wrote:

> Dear Hans,
>
> I saw the C code of LuaMetaTeX and I saw a lot of gotos which is not good
> coding practice. These potions of code which have goto should be refactored.
>
> I am a C programmer, but I know very little of TeX. If you can point me
> towards where should I start for TeX(perhaps TeX Book or TeX for the
> Impatient), I can help with refactoring of code to make is more
> efficient/easier.
>
> --
> Respect,
> Shiv Shankar Dayal
>


-- 
Respect,
Shiv Shankar Dayal

[-- Attachment #1.2: Type: text/html, Size: 1755 bytes --]

[-- Attachment #2: Type: text/plain, Size: 511 bytes --]

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

  reply	other threads:[~2024-01-19  8:34 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 ` Shiv Shankar Dayal [this message]
2024-01-19  8:39   ` [NTG-context] " Taco Hoekwater
2024-01-19  8:43     ` Shiv Shankar Dayal
2024-01-19  9:01   ` Hans Hagen
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=CALJ_jGS_J9dJHZWwY5zrTJPfw2rkr6OapHJU0qmp32gyo+MVPw@mail.gmail.com \
    --to=shivshankar.dayal@gmail.com \
    --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).