Timeline for Why doesn't TikZ's \foreach iterate over the last element of the list?
Current License: CC BY-SA 3.0
27 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2017 at 14:31 | history | edited | David Carlisle | CC BY-SA 3.0 | \\ |
| Apr 13, 2017 at 12:35 | history | edited | CommunityBot | replaced http://tex.stackexchange.com/ with https://tex.stackexchange.com/ | |
| Aug 27, 2014 at 18:43 | history | edited | jub0bs | CC BY-SA 3.0 | added reference to Tikz/PGF v3.0 |
| Jul 18, 2014 at 2:23 | history | bounty awarded | kiss my armpit | ||
| Nov 1, 2013 at 13:53 | history | edited | jub0bs | CC BY-SA 3.0 | refactored answer |
| Oct 31, 2013 at 22:49 | history | edited | jub0bs | CC BY-SA 3.0 | improved answer |
| Sep 22, 2013 at 9:58 | history | edited | jub0bs | CC BY-SA 3.0 | added a reference |
| Aug 18, 2013 at 20:49 | history | wiki removed | Joseph Wright♦ | ||
| Jun 1, 2013 at 19:00 | history | edited | jub0bs | CC BY-SA 3.0 | added 9 characters in body |
| Jun 1, 2013 at 18:01 | history | edited | jub0bs | CC BY-SA 3.0 | deleted 1 characters in body |
| May 31, 2013 at 17:00 | history | edited | jub0bs | CC BY-SA 3.0 | added 820 characters in body |
| May 31, 2013 at 13:28 | history | edited | jub0bs | CC BY-SA 3.0 | added 30 characters in body |
| May 31, 2013 at 13:20 | history | edited | jub0bs | CC BY-SA 3.0 | added a link |
| May 31, 2013 at 13:18 | comment | added | egreg | @percusse Thanks, I was just looking for the fpu library. | |
| May 31, 2013 at 13:17 | comment | added | percusse | @egreg It is indeed the case. You can turn on the fpu library for more precision if you really need it(but mostly you regret that you did that for simple things as this, because then you need to parse the float representation whereever required). Otherwise it is the regular TeX arithmetic. The better approach is to run over the integers and multiply the value inside the body of \foreach. | |
| May 31, 2013 at 13:12 | comment | added | jub0bs | @egreg Subsection 61.3 (about the PGF math engine) in the PGF/TikZ manual states: Currently, the mathematical algorithms are all implemented in TEX. Also, section 62 states: all calculations must not exceed ±16383.99999 at any point, because the underlying computations rely on TEX dimensions. I think the floating-point unit (fpu) you're referring to is not loaded by default but has to be activated explicitly; see section 36. | |
| May 31, 2013 at 13:07 | comment | added | egreg | We were talking about two different things. ;-) OK, the "fixed-point" model is what's used for representing lengths in the context of \the<dimension>. I believe that PGF has its own floating point system, because with TeX's representation only four decimal digits are accurate (and TeX displays at most five). | |
| May 31, 2013 at 12:59 | comment | added | jub0bs | @egreg Doesn't TeX use fixed-point numbers as well as integers? What about section 3 of the article I link to? | |
| May 31, 2013 at 12:57 | comment | added | egreg | TeX doesn't use floating point, but only integer numbers. On the other hand, PGF implements floating point (on top of TeX's integer arithmetic). I don't think TeX's arithmetic has a role in this problem. As far as I know, TeX always truncates when doing divisions. | |
| May 31, 2013 at 12:33 | history | edited | jub0bs | CC BY-SA 3.0 | added 153 characters in body |
| May 31, 2013 at 12:28 | history | edited | jub0bs | CC BY-SA 3.0 | added 153 characters in body |
| May 31, 2013 at 12:13 | history | edited | jub0bs | CC BY-SA 3.0 | deleted 1 characters in body |
| May 31, 2013 at 11:43 | history | edited | jub0bs | CC BY-SA 3.0 | added 15 characters in body |
| May 31, 2013 at 11:37 | history | edited | jub0bs | CC BY-SA 3.0 | added 15 characters in body |
| May 31, 2013 at 11:30 | history | edited | jub0bs | CC BY-SA 3.0 | added 98 characters in body |
| May 31, 2013 at 11:21 | vote | accept | in_mathematica_we_trust | ||
| May 31, 2013 at 11:20 | history | answered | jub0bs | CC BY-SA 3.0 |