unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: guile-devel@gnu.org
Subject: Re: Logo baseline
Date: Sun, 19 Jan 2020 18:40:09 +0100	[thread overview]
Message-ID: <87sgkb4a6e.fsf@web.de> (raw)
In-Reply-To: <31206882-b2d8-dd62-e7eb-d0d1748f4614@gmail.com>


Matt Wette <matt.wette@gmail.com> writes:

> On 1/19/20 6:11 AM, Arne Babenhauserheide wrote:
>> Ludovic Courtès <ludo@gnu.org> writes:
>>> Other adjectives I proposed (fast, functional) don’t quite apply to
>>> these, though.
>> Functional doesn’t apply to Guile much better than to CPython.
>
> I think "functional" is used in the formal sense.
> The term applies to Scheme, Haskell, SML: e.g., they iterate through
> recursion.
Is this also true for the do-loop in Scheme?
> Python, Lua, Perl, Javascript are imperative: e.g., they iterate
> through i=i+1.
That is a result of missing tail recursion.

I understood functional in the no-sideeffects sense — which nowadays is
more a matter of programming style than of the language, though
different languages make it easier or harder.

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken



  reply	other threads:[~2020-01-19 17:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-18 14:08 Logo baseline Ludovic Courtès
2020-01-18 14:33 ` Amirouche Boubekki
2020-01-18 15:08 ` Linus Björnstam
2020-01-18 17:05 ` Matt Wette
2020-01-18 19:40 ` Nala Ginrut
2020-01-18 22:22 ` Arne Babenhauserheide
2020-01-18 22:57 ` Thomas Morley
2020-01-18 23:47   ` Arne Babenhauserheide
2020-01-19 11:21     ` Ludovic Courtès
2020-01-19 14:11       ` Arne Babenhauserheide
2020-01-19 14:59         ` Matt Wette
2020-01-19 17:40           ` Arne Babenhauserheide [this message]
2020-01-20  8:35         ` Ludovic Courtès
2020-01-19  8:14 ` Jan Nieuwenhuizen

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=87sgkb4a6e.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=guile-devel@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).