References: <1438598845.15593.28.camel@sipsolutions.net>
            <55BF4AAE.5010002@nag.co.uk>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-AmWyFGi4PJDMxGp5/tmT"
Mime-Version: 1.0
Message-ID:  <1438604337.15593.45.camel@sipsolutions.net>
Date:         Mon, 3 Aug 2015 14:18:57 +0200
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Benjamin Berg <benjamin@SIPSOLUTIONS.NET>
Subject: Re: Difference between \addtocounter and \int_gincr inside tabularx
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <55BF4AAE.5010002@nag.co.uk>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

--=-AmWyFGi4PJDMxGp5/tmT
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

On Mo, 2015-08-03 at 12:04 +0100, David Carlisle wrote:
> On 03/08/2015 11:47, Benjamin Berg wrote:
> > I am having trouble to understand what the difference between
> > \addtocounter and \int_gincr:N is. When used inside a tabularx
> > environment, the \int_* functions do not work correctly, but the normal
> > LaTeX counters do.
> >=20
> > Maybe the idea of even using counters in a tabularx environment like
> > this is totally wrong[1], but it feels to me like the two commands
> > should behave in the same way. So either I am not grasping some
> > concepts (feel free to just point me to an explanation) or there might
> > even be a small bug.
> >=20
> > So, the attached document will print two tables. For each cell the
> > output of "\int_use:N \g_test_int,~\thetestcount" is displayed. The
> > counter is behaving as I expect while the \g_test_int has different
> > values inside tabularx.
> >=20
> >=20
> > tabularx:
> > 3, 1    4, 2    1, 3    2, 4
> > 3, 1    4, 2
> >=20
> > and tabular:
> > 1, 1    2, 2    3, 3    4, 4
> > 1, 1    2, 2
> >=20
> > It looks like this has to do with the fact that in the second row there
> > are empty cells. But it still baffles me, that the latex counters
> > behave correctly, while latex 3 integers do not.
> >=20
> > Regards,
> > Benjamin
> >=20
> > [1] It is very likely that I will drop the tabularx anyways.
> >=20
>=20
>=20
> tabularx typesets its body multiple times with trial settings to find
> the right widths. So in general any command that is doing anything with
> global side effects like incrementing a counter will increment multiple
> times.
>=20
> You would see the same with plain tex syntax \newcounter\foo.... if you u=
se
> \global\advance\foo 1
> inside tabularx.
>=20
> latex counters have a reset mechanism (designed for use with restoring
> counters after \include, mostly) tabularx uses this to restore all
> counters at the start of every trial setting.
>=20
> \hfuzz is \maxdimen in trials so you can avoid incremengting counters
> during trials with
>=20
> \ifdim\hfuzz<\maxdimen
> ...
>=20
> but sometimes your code needs to increment and then restore, which is a
> bit more work.

Ah, now that makes a lot of sense, thanks for explaining! :)

I guess I was under the impression that tabularx required multiple
latex calls, instead of doing multiple trail runs during one latex run.
And I had no idea there was code to reset the global scope to some
extend.

Best solution for me will be to replace the tabularx use with a normal
tabular or even a tabbing environment.

Benjamin
--=-AmWyFGi4PJDMxGp5/tmT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEABECAAYFAlW/XDEACgkQJddvdAxOva4LCACfQvtu3LXFhBwn8mc9A/ofwYeK
w/IAn2gQiqHf6AJGltIkPxf8CEzdr71X
=HpdV
-----END PGP SIGNATURE-----

--=-AmWyFGi4PJDMxGp5/tmT--