emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: table: problem with nan and if
Date: Tue, 22 Jun 2021 14:35:19 -0400	[thread overview]
Message-ID: <87zgvhg32w.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 8735taieu3.fsf@mat.ucm.es

Uwe Brauer <oub@mat.ucm.es> writes:

>> Uwe Brauer <oub@mat.ucm.es> writes:
>> I'm not very familiar with calc, but am wondering if the issue is the
>> 'nan'. In many languages, a nan is a 'polluting' variable i.e. once you
>> have a nan as a form anywhere in your calculation, the result will
>> always be a nan. Many languages actually have a special function to test
>> for a nan because it isn't actually a 'value'. Don't know if this is the
>> case with calc. 
> Yeah, when I googled, I found complains about nan using in calc but I
> did not really found an working alternative.
>> Perhaps an alternative strategy might help. Could you address what is
>> generating the nan and change that so that it generates something else,
>> possibly even a blank string and avoid the nan altogether? 
> I tried nil and other expressions but non really worked, so maybe a calc
> guru could clarify?

Could you write the formulas in lisp instead? You might be able to control
things more easily:

  (info "(org) Formula syntax for Lisp")


"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

  reply	other threads:[~2021-06-22 18:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 15:05 table: problem with nan and if Uwe Brauer
2021-06-21 16:28 ` Eric S Fraga
2021-06-21 18:58   ` Uwe Brauer
2021-06-22  7:44     ` Eric S Fraga
2021-06-22  7:51       ` tbanelwebmin
2021-06-22  9:03         ` Uwe Brauer
2021-06-22  8:55       ` Uwe Brauer
2021-06-21 22:26 ` Tim Cross
2021-06-22  6:38   ` Uwe Brauer
2021-06-22 18:35     ` Nick Dokos [this message]
2021-06-23  8:26       ` Uwe Brauer

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgvhg32w.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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.
Code repositories for project(s) associated with this public inbox


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 read-only IMAP folder(s) and NNTP newsgroup(s).