Can I defend against “Dimension too large” errors?Does (La)TeX have error catching capabilities?“Dimension too large” error with too many tikzmarksDimension too large while plotting with pgfplotspgfplots “dimension too large” with 3D graphic from external sourceTikZ Dimension too large Matrix TransformTikz: Error “dimension too large” when decorating arc! Dimension too large. in x-y plot“Dimension too large” with data computed and/or importedEvery time there is a LaTeX error, I have to delete my aux file. Counter too largePGF Dimension too largeDimension too large with width=0.75textwidth“Dimension too large” error with too many tikzmarks
Count rotary dial pulses in a phone number (including letters)
Access to the path 'c:somepath' is denied for MSSQL CLR
Which European Languages are not Indo-European?
Compaq Portable vs IBM 5155 Portable PC
Is "cool" appropriate or offensive to use in IMs?
Ethical issue - how can I better document what is happening?
Why would Ryanair allow me to book this journey through a third party, but not through their own website?
Does pair production happen even when the photon is around a neutron?
Looking for a soft substance that doesn't dissolve underwater
What could a self-sustaining lunar colony slowly lose that would ultimately prove fatal?
What is a Power on Reset IC?
Can a British citizen living in France vote in both France and Britain in the European Elections?
What does $!# mean in Shell scripting?
Count Even Digits In Number
Why are GND pads often only connected by four traces?
The art of clickbait captions
Popcorn is the only acceptable snack to consume while watching a movie
Why did Jon Snow admit his fault in S08E06?
Best material to absorb as much light as possible
Why did Theresa May offer a vote on a second Brexit referendum?
When the Torah was almost lost and one (or several) Rabbis saved it?
How to let other coworkers know that I don't share my coworker's political views?
I know that there is a preselected candidate for a position to be filled at my department. What should I do?
Can a person survive on blood in place of water?
Can I defend against “Dimension too large” errors?
Does (La)TeX have error catching capabilities?“Dimension too large” error with too many tikzmarksDimension too large while plotting with pgfplotspgfplots “dimension too large” with 3D graphic from external sourceTikZ Dimension too large Matrix TransformTikz: Error “dimension too large” when decorating arc! Dimension too large. in x-y plot“Dimension too large” with data computed and/or importedEvery time there is a LaTeX error, I have to delete my aux file. Counter too largePGF Dimension too largeDimension too large with width=0.75textwidth“Dimension too large” error with too many tikzmarks
I'm trying to debug the error in "Dimension too large" error with too many tikzmarks which involves getting a Dimension too large
error (duh). I have my suspicions as to what is causing it, and also a suspicion that there will be situations that mean that I can't eliminate the possibility of it occurring altogether.
Is there any way to defend against this error? What I would really like is something like a try ... except ...
block. Does that exist?
Here's a MWE to play around with:
documentclassarticle
newdimenad
newdimenbd
ad=16383ptrelax
bd=2ad
showthead
showthebd
begindocument
enddocument
Essentially, I would like to be able to wrap the bd=2ad
in something that allows me to define an alternative if it threatens to trigger the dreaded Dimension too large
error.
errors dimensions
add a comment |
I'm trying to debug the error in "Dimension too large" error with too many tikzmarks which involves getting a Dimension too large
error (duh). I have my suspicions as to what is causing it, and also a suspicion that there will be situations that mean that I can't eliminate the possibility of it occurring altogether.
Is there any way to defend against this error? What I would really like is something like a try ... except ...
block. Does that exist?
Here's a MWE to play around with:
documentclassarticle
newdimenad
newdimenbd
ad=16383ptrelax
bd=2ad
showthead
showthebd
begindocument
enddocument
Essentially, I would like to be able to wrap the bd=2ad
in something that allows me to define an alternative if it threatens to trigger the dreaded Dimension too large
error.
errors dimensions
1
Some time ago I asked about thetry ... except ...
thing, but it doesn't appear to exist (unfortunately).
– Phelype Oleinik
11 hours ago
Can't you use something like thefpu
orfp
libraries to check first whether or not the value is too large?
– marmot
11 hours ago
add a comment |
I'm trying to debug the error in "Dimension too large" error with too many tikzmarks which involves getting a Dimension too large
error (duh). I have my suspicions as to what is causing it, and also a suspicion that there will be situations that mean that I can't eliminate the possibility of it occurring altogether.
Is there any way to defend against this error? What I would really like is something like a try ... except ...
block. Does that exist?
Here's a MWE to play around with:
documentclassarticle
newdimenad
newdimenbd
ad=16383ptrelax
bd=2ad
showthead
showthebd
begindocument
enddocument
Essentially, I would like to be able to wrap the bd=2ad
in something that allows me to define an alternative if it threatens to trigger the dreaded Dimension too large
error.
errors dimensions
I'm trying to debug the error in "Dimension too large" error with too many tikzmarks which involves getting a Dimension too large
error (duh). I have my suspicions as to what is causing it, and also a suspicion that there will be situations that mean that I can't eliminate the possibility of it occurring altogether.
Is there any way to defend against this error? What I would really like is something like a try ... except ...
block. Does that exist?
Here's a MWE to play around with:
documentclassarticle
newdimenad
newdimenbd
ad=16383ptrelax
bd=2ad
showthead
showthebd
begindocument
enddocument
Essentially, I would like to be able to wrap the bd=2ad
in something that allows me to define an alternative if it threatens to trigger the dreaded Dimension too large
error.
errors dimensions
errors dimensions
asked 11 hours ago
Loop SpaceLoop Space
114k30310611
114k30310611
1
Some time ago I asked about thetry ... except ...
thing, but it doesn't appear to exist (unfortunately).
– Phelype Oleinik
11 hours ago
Can't you use something like thefpu
orfp
libraries to check first whether or not the value is too large?
– marmot
11 hours ago
add a comment |
1
Some time ago I asked about thetry ... except ...
thing, but it doesn't appear to exist (unfortunately).
– Phelype Oleinik
11 hours ago
Can't you use something like thefpu
orfp
libraries to check first whether or not the value is too large?
– marmot
11 hours ago
1
1
Some time ago I asked about the
try ... except ...
thing, but it doesn't appear to exist (unfortunately).– Phelype Oleinik
11 hours ago
Some time ago I asked about the
try ... except ...
thing, but it doesn't appear to exist (unfortunately).– Phelype Oleinik
11 hours ago
Can't you use something like the
fpu
or fp
libraries to check first whether or not the value is too large?– marmot
11 hours ago
Can't you use something like the
fpu
or fp
libraries to check first whether or not the value is too large?– marmot
11 hours ago
add a comment |
1 Answer
1
active
oldest
votes
Using l3fp
to make a wrapper macro which checks if the dimension exceeds c_max_dim
(or maxdimen
or 16383.99999pt
) and uses a fallback value (which I set to c_max_dim
itself) in case the assignment exceeds it:
documentclassarticle
usepackageexpl3
ExplSyntaxOn
cs_new:Npn trydim #1
exp_args:Nf
__loopspace_try_dim:nn fp_eval:n #1 #1
cs_new:Npn __loopspace_try_dim:nn #1 #2
fp_compare:nNnTF abs(#1) > c_max_dim
% Exception code
dim_use:N c_max_dim
% Success code
% Using dim_eval:n to maintain TeX's behaviour,
% but you can replace by #1, which is the result of fp_eval:n
dim_eval:n #2
ExplSyntaxOff
newdimenad
newdimenbd
ad=trydim16383pt
bd=trydim2ad
showthead
showthebd
begindocument
enddocument
This prints to the terminal:
> 16383.0pt.
l.31 showthead
?
> 16383.99998pt.
l.32 showthebd
?
The "exception code" is what you intend to do if the value exceeds c_max_dim
. I used the dim_use:N c_max_dim
to get the maximum value possible.
The "success code", you guessed, is when the value is within the allowed range. I used dim_eval:n #2
because there are controversies on the accuracy of l3fp
, so the result obeys TeX's rules as long as they are valid. Of course you can change that to fp_eval:n #2
(or, for the matter, #1
, which is the fp_eval:n
'ed dimension).
Or, if you prefer, an inline fallback value:
documentclassarticle
usepackageexpl3
ExplSyntaxOn
cs_new:Npn trydim #1 #2
exp_args:Nf
__loopspace_try_dim:nnTF fp_eval:n #1
#1 #2
prg_new_conditional:Npnn __loopspace_try_dim:nn #1 T, F, TF
fp_compare:nNnTF abs(#1) > c_max_dim
prg_return_false:
prg_return_true:
ExplSyntaxOff
newdimenad
newdimenbd
ad=trydim16383pt0pt
bd=trydim2ad10pt
showthead
showthebd
begindocument
enddocument
Which prints:
> 16383.0pt.
l.31 showthead
?
> 10.0pt.
l.32 showthebd
?
It's not the accuracy ofl3fp
that's a bit interesting with dimens, it's how you decide to deal with the conversion: there are equally-valid paths with different outcomes. Personally, I'd always usedim_to_fp:n
for these.
– Joseph Wright♦
11 hours ago
1
Looks fabulous! Thank you.
– Loop Space
11 hours ago
@JosephWright But here, since we expect aDimension too large
,dim_to_fp:n
could fail, right?
– Phelype Oleinik
11 hours ago
@PhelypeOleinik Yes, that's true: I just meant in general. (The team are actively discussing what the right approach is.)
– Joseph Wright♦
11 hours ago
@JosephWright Oh, right, about the other question. I'm curious about that now :-) (thanks for the pointer todim_to_fp:n
; I didn't know it before)
– Phelype Oleinik
11 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f492349%2fcan-i-defend-against-dimension-too-large-errors%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Using l3fp
to make a wrapper macro which checks if the dimension exceeds c_max_dim
(or maxdimen
or 16383.99999pt
) and uses a fallback value (which I set to c_max_dim
itself) in case the assignment exceeds it:
documentclassarticle
usepackageexpl3
ExplSyntaxOn
cs_new:Npn trydim #1
exp_args:Nf
__loopspace_try_dim:nn fp_eval:n #1 #1
cs_new:Npn __loopspace_try_dim:nn #1 #2
fp_compare:nNnTF abs(#1) > c_max_dim
% Exception code
dim_use:N c_max_dim
% Success code
% Using dim_eval:n to maintain TeX's behaviour,
% but you can replace by #1, which is the result of fp_eval:n
dim_eval:n #2
ExplSyntaxOff
newdimenad
newdimenbd
ad=trydim16383pt
bd=trydim2ad
showthead
showthebd
begindocument
enddocument
This prints to the terminal:
> 16383.0pt.
l.31 showthead
?
> 16383.99998pt.
l.32 showthebd
?
The "exception code" is what you intend to do if the value exceeds c_max_dim
. I used the dim_use:N c_max_dim
to get the maximum value possible.
The "success code", you guessed, is when the value is within the allowed range. I used dim_eval:n #2
because there are controversies on the accuracy of l3fp
, so the result obeys TeX's rules as long as they are valid. Of course you can change that to fp_eval:n #2
(or, for the matter, #1
, which is the fp_eval:n
'ed dimension).
Or, if you prefer, an inline fallback value:
documentclassarticle
usepackageexpl3
ExplSyntaxOn
cs_new:Npn trydim #1 #2
exp_args:Nf
__loopspace_try_dim:nnTF fp_eval:n #1
#1 #2
prg_new_conditional:Npnn __loopspace_try_dim:nn #1 T, F, TF
fp_compare:nNnTF abs(#1) > c_max_dim
prg_return_false:
prg_return_true:
ExplSyntaxOff
newdimenad
newdimenbd
ad=trydim16383pt0pt
bd=trydim2ad10pt
showthead
showthebd
begindocument
enddocument
Which prints:
> 16383.0pt.
l.31 showthead
?
> 10.0pt.
l.32 showthebd
?
It's not the accuracy ofl3fp
that's a bit interesting with dimens, it's how you decide to deal with the conversion: there are equally-valid paths with different outcomes. Personally, I'd always usedim_to_fp:n
for these.
– Joseph Wright♦
11 hours ago
1
Looks fabulous! Thank you.
– Loop Space
11 hours ago
@JosephWright But here, since we expect aDimension too large
,dim_to_fp:n
could fail, right?
– Phelype Oleinik
11 hours ago
@PhelypeOleinik Yes, that's true: I just meant in general. (The team are actively discussing what the right approach is.)
– Joseph Wright♦
11 hours ago
@JosephWright Oh, right, about the other question. I'm curious about that now :-) (thanks for the pointer todim_to_fp:n
; I didn't know it before)
– Phelype Oleinik
11 hours ago
add a comment |
Using l3fp
to make a wrapper macro which checks if the dimension exceeds c_max_dim
(or maxdimen
or 16383.99999pt
) and uses a fallback value (which I set to c_max_dim
itself) in case the assignment exceeds it:
documentclassarticle
usepackageexpl3
ExplSyntaxOn
cs_new:Npn trydim #1
exp_args:Nf
__loopspace_try_dim:nn fp_eval:n #1 #1
cs_new:Npn __loopspace_try_dim:nn #1 #2
fp_compare:nNnTF abs(#1) > c_max_dim
% Exception code
dim_use:N c_max_dim
% Success code
% Using dim_eval:n to maintain TeX's behaviour,
% but you can replace by #1, which is the result of fp_eval:n
dim_eval:n #2
ExplSyntaxOff
newdimenad
newdimenbd
ad=trydim16383pt
bd=trydim2ad
showthead
showthebd
begindocument
enddocument
This prints to the terminal:
> 16383.0pt.
l.31 showthead
?
> 16383.99998pt.
l.32 showthebd
?
The "exception code" is what you intend to do if the value exceeds c_max_dim
. I used the dim_use:N c_max_dim
to get the maximum value possible.
The "success code", you guessed, is when the value is within the allowed range. I used dim_eval:n #2
because there are controversies on the accuracy of l3fp
, so the result obeys TeX's rules as long as they are valid. Of course you can change that to fp_eval:n #2
(or, for the matter, #1
, which is the fp_eval:n
'ed dimension).
Or, if you prefer, an inline fallback value:
documentclassarticle
usepackageexpl3
ExplSyntaxOn
cs_new:Npn trydim #1 #2
exp_args:Nf
__loopspace_try_dim:nnTF fp_eval:n #1
#1 #2
prg_new_conditional:Npnn __loopspace_try_dim:nn #1 T, F, TF
fp_compare:nNnTF abs(#1) > c_max_dim
prg_return_false:
prg_return_true:
ExplSyntaxOff
newdimenad
newdimenbd
ad=trydim16383pt0pt
bd=trydim2ad10pt
showthead
showthebd
begindocument
enddocument
Which prints:
> 16383.0pt.
l.31 showthead
?
> 10.0pt.
l.32 showthebd
?
It's not the accuracy ofl3fp
that's a bit interesting with dimens, it's how you decide to deal with the conversion: there are equally-valid paths with different outcomes. Personally, I'd always usedim_to_fp:n
for these.
– Joseph Wright♦
11 hours ago
1
Looks fabulous! Thank you.
– Loop Space
11 hours ago
@JosephWright But here, since we expect aDimension too large
,dim_to_fp:n
could fail, right?
– Phelype Oleinik
11 hours ago
@PhelypeOleinik Yes, that's true: I just meant in general. (The team are actively discussing what the right approach is.)
– Joseph Wright♦
11 hours ago
@JosephWright Oh, right, about the other question. I'm curious about that now :-) (thanks for the pointer todim_to_fp:n
; I didn't know it before)
– Phelype Oleinik
11 hours ago
add a comment |
Using l3fp
to make a wrapper macro which checks if the dimension exceeds c_max_dim
(or maxdimen
or 16383.99999pt
) and uses a fallback value (which I set to c_max_dim
itself) in case the assignment exceeds it:
documentclassarticle
usepackageexpl3
ExplSyntaxOn
cs_new:Npn trydim #1
exp_args:Nf
__loopspace_try_dim:nn fp_eval:n #1 #1
cs_new:Npn __loopspace_try_dim:nn #1 #2
fp_compare:nNnTF abs(#1) > c_max_dim
% Exception code
dim_use:N c_max_dim
% Success code
% Using dim_eval:n to maintain TeX's behaviour,
% but you can replace by #1, which is the result of fp_eval:n
dim_eval:n #2
ExplSyntaxOff
newdimenad
newdimenbd
ad=trydim16383pt
bd=trydim2ad
showthead
showthebd
begindocument
enddocument
This prints to the terminal:
> 16383.0pt.
l.31 showthead
?
> 16383.99998pt.
l.32 showthebd
?
The "exception code" is what you intend to do if the value exceeds c_max_dim
. I used the dim_use:N c_max_dim
to get the maximum value possible.
The "success code", you guessed, is when the value is within the allowed range. I used dim_eval:n #2
because there are controversies on the accuracy of l3fp
, so the result obeys TeX's rules as long as they are valid. Of course you can change that to fp_eval:n #2
(or, for the matter, #1
, which is the fp_eval:n
'ed dimension).
Or, if you prefer, an inline fallback value:
documentclassarticle
usepackageexpl3
ExplSyntaxOn
cs_new:Npn trydim #1 #2
exp_args:Nf
__loopspace_try_dim:nnTF fp_eval:n #1
#1 #2
prg_new_conditional:Npnn __loopspace_try_dim:nn #1 T, F, TF
fp_compare:nNnTF abs(#1) > c_max_dim
prg_return_false:
prg_return_true:
ExplSyntaxOff
newdimenad
newdimenbd
ad=trydim16383pt0pt
bd=trydim2ad10pt
showthead
showthebd
begindocument
enddocument
Which prints:
> 16383.0pt.
l.31 showthead
?
> 10.0pt.
l.32 showthebd
?
Using l3fp
to make a wrapper macro which checks if the dimension exceeds c_max_dim
(or maxdimen
or 16383.99999pt
) and uses a fallback value (which I set to c_max_dim
itself) in case the assignment exceeds it:
documentclassarticle
usepackageexpl3
ExplSyntaxOn
cs_new:Npn trydim #1
exp_args:Nf
__loopspace_try_dim:nn fp_eval:n #1 #1
cs_new:Npn __loopspace_try_dim:nn #1 #2
fp_compare:nNnTF abs(#1) > c_max_dim
% Exception code
dim_use:N c_max_dim
% Success code
% Using dim_eval:n to maintain TeX's behaviour,
% but you can replace by #1, which is the result of fp_eval:n
dim_eval:n #2
ExplSyntaxOff
newdimenad
newdimenbd
ad=trydim16383pt
bd=trydim2ad
showthead
showthebd
begindocument
enddocument
This prints to the terminal:
> 16383.0pt.
l.31 showthead
?
> 16383.99998pt.
l.32 showthebd
?
The "exception code" is what you intend to do if the value exceeds c_max_dim
. I used the dim_use:N c_max_dim
to get the maximum value possible.
The "success code", you guessed, is when the value is within the allowed range. I used dim_eval:n #2
because there are controversies on the accuracy of l3fp
, so the result obeys TeX's rules as long as they are valid. Of course you can change that to fp_eval:n #2
(or, for the matter, #1
, which is the fp_eval:n
'ed dimension).
Or, if you prefer, an inline fallback value:
documentclassarticle
usepackageexpl3
ExplSyntaxOn
cs_new:Npn trydim #1 #2
exp_args:Nf
__loopspace_try_dim:nnTF fp_eval:n #1
#1 #2
prg_new_conditional:Npnn __loopspace_try_dim:nn #1 T, F, TF
fp_compare:nNnTF abs(#1) > c_max_dim
prg_return_false:
prg_return_true:
ExplSyntaxOff
newdimenad
newdimenbd
ad=trydim16383pt0pt
bd=trydim2ad10pt
showthead
showthebd
begindocument
enddocument
Which prints:
> 16383.0pt.
l.31 showthead
?
> 10.0pt.
l.32 showthebd
?
edited 11 hours ago
answered 11 hours ago
Phelype OleinikPhelype Oleinik
28.2k64794
28.2k64794
It's not the accuracy ofl3fp
that's a bit interesting with dimens, it's how you decide to deal with the conversion: there are equally-valid paths with different outcomes. Personally, I'd always usedim_to_fp:n
for these.
– Joseph Wright♦
11 hours ago
1
Looks fabulous! Thank you.
– Loop Space
11 hours ago
@JosephWright But here, since we expect aDimension too large
,dim_to_fp:n
could fail, right?
– Phelype Oleinik
11 hours ago
@PhelypeOleinik Yes, that's true: I just meant in general. (The team are actively discussing what the right approach is.)
– Joseph Wright♦
11 hours ago
@JosephWright Oh, right, about the other question. I'm curious about that now :-) (thanks for the pointer todim_to_fp:n
; I didn't know it before)
– Phelype Oleinik
11 hours ago
add a comment |
It's not the accuracy ofl3fp
that's a bit interesting with dimens, it's how you decide to deal with the conversion: there are equally-valid paths with different outcomes. Personally, I'd always usedim_to_fp:n
for these.
– Joseph Wright♦
11 hours ago
1
Looks fabulous! Thank you.
– Loop Space
11 hours ago
@JosephWright But here, since we expect aDimension too large
,dim_to_fp:n
could fail, right?
– Phelype Oleinik
11 hours ago
@PhelypeOleinik Yes, that's true: I just meant in general. (The team are actively discussing what the right approach is.)
– Joseph Wright♦
11 hours ago
@JosephWright Oh, right, about the other question. I'm curious about that now :-) (thanks for the pointer todim_to_fp:n
; I didn't know it before)
– Phelype Oleinik
11 hours ago
It's not the accuracy of
l3fp
that's a bit interesting with dimens, it's how you decide to deal with the conversion: there are equally-valid paths with different outcomes. Personally, I'd always use dim_to_fp:n
for these.– Joseph Wright♦
11 hours ago
It's not the accuracy of
l3fp
that's a bit interesting with dimens, it's how you decide to deal with the conversion: there are equally-valid paths with different outcomes. Personally, I'd always use dim_to_fp:n
for these.– Joseph Wright♦
11 hours ago
1
1
Looks fabulous! Thank you.
– Loop Space
11 hours ago
Looks fabulous! Thank you.
– Loop Space
11 hours ago
@JosephWright But here, since we expect a
Dimension too large
, dim_to_fp:n
could fail, right?– Phelype Oleinik
11 hours ago
@JosephWright But here, since we expect a
Dimension too large
, dim_to_fp:n
could fail, right?– Phelype Oleinik
11 hours ago
@PhelypeOleinik Yes, that's true: I just meant in general. (The team are actively discussing what the right approach is.)
– Joseph Wright♦
11 hours ago
@PhelypeOleinik Yes, that's true: I just meant in general. (The team are actively discussing what the right approach is.)
– Joseph Wright♦
11 hours ago
@JosephWright Oh, right, about the other question. I'm curious about that now :-) (thanks for the pointer to
dim_to_fp:n
; I didn't know it before)– Phelype Oleinik
11 hours ago
@JosephWright Oh, right, about the other question. I'm curious about that now :-) (thanks for the pointer to
dim_to_fp:n
; I didn't know it before)– Phelype Oleinik
11 hours ago
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f492349%2fcan-i-defend-against-dimension-too-large-errors%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Some time ago I asked about the
try ... except ...
thing, but it doesn't appear to exist (unfortunately).– Phelype Oleinik
11 hours ago
Can't you use something like the
fpu
orfp
libraries to check first whether or not the value is too large?– marmot
11 hours ago