From: "Germán Diago" <germandiago@gmail.com>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: guile-user@gnu.org
Subject: Re: Playing with guile (vs python). Generate file for GDP suitable for gnuplot.
Date: Thu, 02 Feb 2017 08:32:37 +0000 [thread overview]
Message-ID: <CAALp5N4iA349acZTRkL6L6ehFcPw_ofStbFnphvco8XvDCKmAg@mail.gmail.com> (raw)
In-Reply-To: <877f59im6p.fsf@web.de>
El El jue, 2 feb 2017 a las 5:24, Arne Babenhauserheide <arne_bab@web.de>
escribió:
>
> Germán Diago <germandiago@gmail.com> writes:
>
> >> Aside from using a more recent Guile, I do not see obvious
> >> optimizations, however (more exactly: all my tries to speedup the code
> >> only made it slower).
> >
> > I was struggling with using read-line! instead of read-line but
> > experimenting in the command line
> > I cannot figure out how it works actually. read-line! will reuse a
> buffered
> > string. There was lots of time spent there, I am not sure if because of
> > allocations or just because of I/O. If someone could tell me how to do
> it...
>
> One thing I realized now is that you might be able to avoid the
> string->number conversion completely since you’re outputting as text
> anyway. That might save 1/4th of the time (but I did not experiment with
> that now).
True.
> Also I’m not sure whether the "is this a number"-check could be sped up
> by adding specialization for chars in the Scheme-compiler, similar to
> how floating point comparisons were added in the latest release:
>
> https://git.dthompson.us/guile.git/commitdiff/79fa147990021b48a5ede2f33441bc95721fe63d
>
> > Thanks for your time Arne!
>
> Thank you for the challenging problem
Welcome!! :)
next prev parent reply other threads:[~2017-02-02 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 5:19 Playing with guile (vs python). Generate file for GDP suitable for gnuplot Germán Diago
2017-01-31 7:40 ` Alex Vong
2017-01-31 9:41 ` Arne Babenhauserheide
2017-02-01 3:56 ` Germán Diago
2017-02-01 22:24 ` Arne Babenhauserheide
2017-02-02 8:32 ` Germán Diago [this message]
2017-02-11 14:12 ` Ludovic Courtès
2017-03-06 13:50 ` Thien-Thi Nguyen
2017-03-06 21:02 ` Andy Wingo
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.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAALp5N4iA349acZTRkL6L6ehFcPw_ofStbFnphvco8XvDCKmAg@mail.gmail.com \
--to=germandiago@gmail.com \
--cc=arne_bab@web.de \
--cc=guile-user@gnu.org \
/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).