unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: Anthony Quizon <anthoq88@gmail.com>, guile-user@gnu.org
Subject: Re: How to use guile in a development process
Date: Thu, 29 Apr 2021 16:49:07 +0200	[thread overview]
Message-ID: <3a3a34ab9b8aff4b860ec838e5298eb90c137e81.camel@korwin-zmijowski.fr> (raw)
In-Reply-To: <CAPHgq+JxjG8rTc61ZgrBun5_c+X0T67Tf-1Kb4XV6URhBo5n1w@mail.gmail.com>

Le jeudi 29 avril 2021 à 10:35 +1000, Anthony Quizon a écrit :
> But more importantly, what is the typical workflow when using guile?
> Do people write files to the filesystem and load them in the repl to
> try it
> out?

I think there is not anything typical in the Guile community.
I usually execute Guile scripts from the command line and I use the
REPL for exploratory work only. But I feel I should use the REPL more
than I do. I am reading all I can find about REPL practices to find
inspiration.

I follow the TDD workflow. So I run my test harness this way :
$ guile -L . tests/xxxx-test.scm
I fire this command anytime I change a file using a watch-based script.
I edit code using Emacs and its Geiser extension to explore Guile
features.

> Or is there a faster way to do things?

Automation. haha


P.S: would you like to join me to code together so I can show what I
wrote above ?
We could pair-program for 1h :-)

Cheers,
Jérémy




  parent reply	other threads:[~2021-04-29 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  0:35 How to use guile in a development process Anthony Quizon
2021-04-29  2:19 ` Nala Ginrut
2021-04-29  7:26   ` Dr. Arne Babenhauserheide
2021-04-29  8:16 ` Adriano Peluso
2021-04-29 14:49 ` Jérémy Korwin-Zmijowski [this message]
2021-04-30  2:34 ` Tim Meehan
2021-04-30 11:22   ` Leo Butler

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=3a3a34ab9b8aff4b860ec838e5298eb90c137e81.camel@korwin-zmijowski.fr \
    --to=jeremy@korwin-zmijowski.fr \
    --cc=anthoq88@gmail.com \
    --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).