unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: CToID <funk443@yandex.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Is it possible to write program only in Guile?
Date: Wed, 18 Oct 2023 13:12:08 +0000	[thread overview]
Message-ID: <f65c3a8c-576a-4708-9486-3384c9632ccb@posteo.de> (raw)
In-Reply-To: <d57fe799-0910-4a2c-b41f-d96de746764b@yandex.com>

On 10/18/23 12:23, CToID wrote:
> Hello guys, a common lisper here.  I've recently developed some interests in 
> Guile, and wonder if I can make a program entirely written in Guile.
>
> The reason why I am asking this question is because Guile seems to be designed 
> as an extension language that will be embedded into other programs.
>
Hello CToID!

When I was first looking at GNU Guile, I had the same question. This might be 
due to it being promoted as an extension language on the official website (I think).

Yes it is possible to write programs exclusively in GNU Guile : ) Just like you 
can write whole programs with Racket or other similar languages.

It is one of the more used Scheme dialects. At least I think it is, from the 
perspective of my own bubble.

Many exciting developments happened over the last 1–2 (or is it 3?) years. There 
is the whole Guix thing for example. Recently for example Guile Hoot, if you 
want to look that up. However, as a non-mainstream language, of course you might 
also come across some rougher corners and might need to implement things on your 
own or ask around what others already have. People on the mailing list are often 
helpful.

Welcome!

Best regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl




      parent reply	other threads:[~2023-10-18 13:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 10:23 Is it possible to write program only in Guile? CToID
2023-10-18 12:51 ` Basile Starynkevitch
2023-10-18 13:31   ` CToID
2023-10-18 13:36     ` Basile Starynkevitch
2023-10-18 14:43     ` Greg Troxel
2023-10-18 15:06       ` CToID
2023-10-18 15:50         ` Hans Åberg
2023-10-18 20:24           ` Janneke Nieuwenhuizen
2023-10-18 16:11         ` Thompson, David
2023-10-19  4:52       ` tomas
2023-10-19 11:18         ` wolf
2023-10-20  4:35           ` tomas
2023-10-18 13:10 ` Olivier Dion
2023-10-18 13:32   ` Marc Chantreux
2023-10-18 13:44     ` Olivier Dion
2023-10-18 18:49       ` wolf
2023-10-18 19:14         ` Olivier Dion
2023-10-20 10:19         ` Marc Chantreux
2023-10-18 13:12 ` Zelphir Kaltstahl [this message]

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=f65c3a8c-576a-4708-9486-3384c9632ccb@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=funk443@yandex.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).