unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: wolf <wolf@wolfsden.cz>
To: guile-user@gnu.org
Subject: Recommended project structure
Date: Fri, 9 Jun 2023 00:43:45 +0200	[thread overview]
Message-ID: <ZIJZoZP8yZaRo9jk@ws> (raw)

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

Greetings,

I am starting a small, personal project and I want to write it in GNU Guile,
since I really like it so far.  However, since one of the major goals is for
this to be a learning experience and doing it "the right way", I wanted to ask
about recommended/standard project structure for Guile projects.  I found
this[0] tutorial, but it is from 2017, which is quite some time back (I feel
old).

So I wanted to ask, does the tutorial describe best practices even in 2023?  If
not, what would be a good reading on this topic?

Thanks,

W.

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2023-06-08 22:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 22:43 wolf [this message]
2023-06-09  3:33 ` Recommended project structure Olivier Dion via General Guile related discussions
2023-06-09 12:55   ` wolf
2023-06-09 16:17     ` Olivier Dion via General Guile related discussions
2023-06-09 19:33       ` David Pirotte
2023-06-16 23:04         ` wolf
2023-06-09 16:41 ` Thompson, David
2023-06-09 18:40 ` Nala Ginrut

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=ZIJZoZP8yZaRo9jk@ws \
    --to=wolf@wolfsden.cz \
    --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).