From: Fleur Kelpin <fleur@bio.vu.nl>
To: <gsl-discuss@sources.redhat.com>
Subject: fprintf for blocks/vectors: why the \n?
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0112121604530.18376-100000@monodon> (raw)
Hi all,
If the automatic \n in block/fprintf_source.c were to go, people could
provide the format "%g\n" or "%g\t" or anything they like.
This makes it easier to send the output of a time series of vectors to
e.g. gnuplot because one can also print to columns then, instead of
the now compulsory elements below each other.
Or, if backwards compatibility is a concern, maybe provide this in a
second function with slightly different name?
The way things are now, I find I am writing my own for loops for printing,
whereas gsl tries to provide this functionality.
Greetings,
Fleur Kelpin
WARNING: multiple messages have this Message-ID
From: Fleur Kelpin <fleur@bio.vu.nl>
To: <gsl-discuss@sources.redhat.com>
Subject: fprintf for blocks/vectors: why the \n?
Date: Wed, 05 Dec 2001 12:20:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0112121604530.18376-100000@monodon> (raw)
Message-ID: <20011205122000.BiK-G7s4Rg4hGFBz6LUlVVZBEcjVI7FeuCTjqCVEIEo@z> (raw)
Hi all,
If the automatic \n in block/fprintf_source.c were to go, people could
provide the format "%g\n" or "%g\t" or anything they like.
This makes it easier to send the output of a time series of vectors to
e.g. gnuplot because one can also print to columns then, instead of
the now compulsory elements below each other.
Or, if backwards compatibility is a concern, maybe provide this in a
second function with slightly different name?
The way things are now, I find I am writing my own for loops for printing,
whereas gsl tries to provide this functionality.
Greetings,
Fleur Kelpin
next reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 Fleur Kelpin [this message]
2001-12-05 12:20 ` Fleur Kelpin
2001-12-19 13:20 ` Brian Gough
2001-12-05 13:33 ` Brian Gough
2001-12-19 13:20 ` Gerard Jungman
2001-12-05 12:20 ` Gerard Jungman
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=Pine.GSO.4.33.0112121604530.18376-100000@monodon \
--to=fleur@bio.vu.nl \
--cc=gsl-discuss@sources.redhat.com \
/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).