From: tsd@tsdye.com (Thomas S. Dye)
To: Thierry Banel <tbanelwebmin@free.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: babel C, C++, D enhancement
Date: Mon, 16 Jun 2014 11:14:35 -1000 [thread overview]
Message-ID: <m2r42oh804.fsf@tsdye.com> (raw)
In-Reply-To: <539F5842.2060209@free.fr> (Thierry Banel's message of "Mon, 16 Jun 2014 22:49:06 +0200")
Aloha Thierry,
How about a user-customizable variable with a default value of
2147483647?
All the best,
Tom
Thierry Banel <tbanelwebmin@free.fr> writes:
> Hi Achim.
>
> You are right, INT_MAX is the C++ constant to compare to.
> It is defined in limits.h
>
> I'm not sure I want to locate limits.h (where is it ? are there several
> versions ?),
> and parse it, all from within Emacs-lisp...
> And this will have to be done for all languages (Python, Perl, Java, and
> so on),
> not just C++.
>
> Or we could assume that INT_MAX is always 2147483647.
> (Which of course is not true).
>
> Not so easy...
>
> Regards
> Thierry
>
> Le 16/06/2014 20:28, Achim Gratz a écrit :
>> Thierry Banel writes:
>>> So Babel C++ may cause problem for large integers.
>>> I am not sure how we can fix this in any case.
>> You'd need to know INT_MAX and give an error for larger values or use an
>> integral type that is large enough to handle Emacs' integer (which would
>> most likely be necessary for any Emacs that uses wide integer).
>>
>>> In the meantime, we can force large values to be declared as doubles by
>>> adding dot zero
>>> like this:
>>>
>>> #+BEGIN_SRC C++ :var large=9876543210 .0
>>> printf ("%g", large);
>>> #+END_SRC
>> That will lose precision, so it may not be the right thing either.
>>
>>
>> Regards,
>> Achim.
>
>
>
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2014-06-16 21:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 1:34 Patch for testing `org-open-at-point' York Zhao
2014-04-11 7:23 ` Nicolas Goaziou
2014-04-11 10:25 ` Bastien
2014-04-12 14:22 ` York Zhao
2014-04-17 18:48 ` Bastien
2014-04-20 19:19 ` Michael Strey
2014-04-20 19:56 ` York Zhao
2014-06-01 1:12 ` York Zhao
2014-06-01 8:53 ` Bastien
2014-06-01 20:15 ` Achim Gratz
2014-06-01 21:14 ` Bastien
2014-06-01 21:58 ` babel C, C++, D enhancement Thierry Banel
2014-06-06 16:31 ` Eric Schulte
2014-06-07 18:19 ` Thierry Banel
2014-06-08 20:19 ` Thierry Banel
2014-06-08 23:22 ` Eric Schulte
2014-06-09 9:40 ` Thierry Banel
2014-06-13 6:51 ` Achim Gratz
2014-06-13 11:47 ` Eric Schulte
2014-06-13 22:07 ` Thierry Banel
2014-06-16 18:28 ` Achim Gratz
2014-06-16 20:49 ` Thierry Banel
2014-06-16 21:14 ` Thomas S. Dye [this message]
2014-06-16 22:24 ` Nick Dokos
2014-06-17 17:16 ` Achim Gratz
2014-06-17 20:51 ` Thierry Banel
2014-06-13 10:55 ` Bastien
2014-06-13 11:58 ` conforming commit messages Was: " Eric Schulte
2014-06-13 14:50 ` Eric Abrahamsen
2014-06-02 19:13 ` Patch for testing `org-open-at-point' Achim Gratz
2014-06-03 7:22 ` Bastien
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
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=m2r42oh804.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=tbanelwebmin@free.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).