public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Oliver Jennrich" <oliver.jennrich@googlemail.com>
To: "Jochen Küpper" <jochen@fhi-berlin.mpg.de>
Cc: gsl-discuss@sourceware.org
Subject: Re: constants update
Date: Thu, 10 Jan 2008 10:19:00 -0000	[thread overview]
Message-ID: <1eaaa6d50801100216u1a204034k13699eb4d4b430af@mail.gmail.com> (raw)
In-Reply-To: <8A45541B-99EC-4628-93B2-7D37095C59C9@fhi-berlin.mpg.de>

On Jan 10, 2008 10:23 AM, Jochen Küpper <jochen@fhi-berlin.mpg.de> wrote:
> Brian,
>
> On 10.01.2008, at 10:01, Jochen Küpper wrote:
>
> > Therefore, someone needs to create a patch for calc-units-
> > update.el, i.e., as the following:
>
>
> here is a patch to upgrade some (very few!) constants to CODATA 2006.
> Hopefully this can also serve someone else as a guide to update more
> values in GSL.

I'm wondering if updating the constants without a possibility to
revert to an earlier version is a good idea.

Would it be useful to have something like

GSL_CONST_MKSA_SPEED_OF_LIGHT_2000
GSL_CONST_MKSA_SPEED_OF_LIGHT_2006

and


GSL_CONST_MKSA_SPEED_OF_LIGHT

to be either of the two, depending on a #define?
>
>
> Greetings,
> Jochen
> --
> Einigkeit und Recht und Freiheit                http://www.Jochen-
> Kuepper.de
>      Liberté, Égalité, Fraternité                GnuPG key: CC1B0B4D
>          Sex, drugs and rock-n-roll
>
>
>
>



-- 
Space -- the final frontier

  reply	other threads:[~2008-01-10 10:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 17:07 Richard Mathar
2008-01-10  9:02 ` Jochen Küpper
2008-01-10  9:23   ` Jochen Küpper
2008-01-10 10:19     ` Oliver Jennrich [this message]
2008-01-10 11:21       ` Jochen Küpper
2008-01-10 12:39       ` Brian Gough
2008-01-10 22:22     ` Brian Gough
  -- strict thread matches above, loose matches on Subject: below --
2008-01-06 23:15 Jochen Küpper
2008-01-08 18:42 ` Brian Gough

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

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

  git send-email \
    --in-reply-to=1eaaa6d50801100216u1a204034k13699eb4d4b430af@mail.gmail.com \
    --to=oliver.jennrich@googlemail.com \
    --cc=gsl-discuss@sourceware.org \
    --cc=jochen@fhi-berlin.mpg.de \
    /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.
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).