From: Taco Hoekwater <taco@elvenkind.com>
Cc: ntg-context@ntg.nl
Subject: Re: Number conversions (Was Re: My ideas for tooltips)
Date: Mon, 19 Feb 2001 13:38:13 +0100 [thread overview]
Message-ID: <3A9113B5.513A6D91@elvenkind.com> (raw)
In-Reply-To: <3.0.6.32.20010219121826.017fd480@server-1>
Hans Hagen wrote:
>
> I'l have a look at it. A few (quick) remarks:
>
> - is the commalist really needed?
I think so, yes. (the one in \converttoradix). The
macro \buildcommalist that is part of \convertfromradix has a badly
chosen name, it (currently) doesn't involve lists at all.
I intend to create a version without size limits, and that means
I need a way to process partial numbers safely.
Life would be a lot easier if TeX had a \remainder and a \modulo
operation. This code looks a lot like assembly programming =)
> - can we use etex expr to create a fully expandable alternative
Unlikely for \converttoradix, but maybe doable from \convertfromradix.
What *precisely* do you need?
> also:
>
> - i will encapsulate this into something \define
Wait for a while, there are still many many improvements possible.
--
groeten,
Taco
next prev parent reply other threads:[~2001-02-19 12:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 21:34 My ideas for tooltips Giuseppe Bilotta
2001-02-15 8:13 ` Taco Hoekwater
2001-02-16 10:45 ` Giuseppe Bilotta
2001-02-16 12:21 ` Taco Hoekwater
2001-02-16 21:45 ` Uwe Koloska
2001-02-17 17:25 ` Taco Hoekwater
[not found] ` <000501c0992c$f7eeb180$a3ccfea9@nuovo>
2001-02-17 23:28 ` Number conversions (Was Re: My ideas for tooltips) Taco Hoekwater
2001-02-19 11:18 ` Hans Hagen
2001-02-19 12:38 ` Taco Hoekwater [this message]
2001-02-19 14:45 ` Hans Hagen
2001-02-19 10:39 ` My ideas for tooltips Hans Hagen
2001-02-16 12:38 ` Hans Hagen
2001-02-16 18:57 ` Giuseppe Bilotta
2001-02-19 11:25 ` Hans Hagen
2001-02-19 22:48 ` Giuseppe Bilotta
2001-02-20 11:35 ` Hans Hagen
2001-02-20 22:49 ` Giuseppe Bilotta
2001-03-12 8:16 ` 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=3A9113B5.513A6D91@elvenkind.com \
--to=taco@elvenkind.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).