ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: (pdfe)TeX register clash?
Date: Thu, 15 Nov 2001 09:25:19 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20011115092246.0403c490@server-1> (raw)
In-Reply-To: <3BF3408D.D0F1A47E@idaccr.org>

At 11:12 PM 11/14/2001 -0500, you wrote:
>I'm using ConTeXt with pdfeTeX to typeset a large manuscript, and things
>have been going very well, but I had to work around the following problem.
>
>When I defined variables using the plain TeX methods, e.g.
>
>\newcount\Mycount
>\newbox\Mybox
>
>and started using these in my macros, it seemed to confuse ConTeXt about
>which pages were left pages and which were right pages.  If I just blindly
>say
>
>\chardef\Mycount=200
>\chardef\Mybox=200
>
>then everything works.  It seems ConTeXt and I were using the same counter.
>
>What is the preferred method for allocating variables (TeX registers) for
>my own macros?  My apologies if this is a FAQ.  I couldn't find a FAQ file
>for this mailing list.

Context offers \newcount and \newbox (although the implementation is 
adapted to etex's >256 register count; i don't use the original etex macros).

So, there must be something else going on. How does the macro that uses the 
counter look? Maybe there is some unsafe testing going on there (lookahead 
problem).

Hans

-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


  reply	other threads:[~2001-11-15  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15  4:12 F. Miller Maley
2001-11-15  8:25 ` Hans Hagen [this message]
2001-11-16  1:07   ` F. Miller Maley
2001-11-16  8:41     ` 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=5.1.0.14.1.20011115092246.0403c490@server-1 \
    --to=pragma@wxs.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).