unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Luis Felipe <sirgazil@zoho.com>
To: Nikolaos Chatzikonstantinou <nchatz314@gmail.com>, guile-user@gnu.org
Subject: Re: Some issues with guile
Date: Fri, 26 Apr 2024 15:21:04 +0000	[thread overview]
Message-ID: <e5d3d38a-4fb7-ae6f-8e4b-56fba5c26748@zoho.com> (raw)
In-Reply-To: <CAAQmekcHf-JQm4hV+WyecBFCAYatZVDKcTKbtRO=Yt-ObzmDRQ@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1863 bytes --]

Hi Nikolaos,

El 26/04/24 a las 7:05, Nikolaos Chatzikonstantinou escribió:
> 2. Documentation extraction sucks.
[...]
>    - documentá in its page does not include an example of how it works!
>      Not a line of code to explain to the user which documentation is
>      extracted. I could not understand how to use it.

Yeah, I didn't want to include how to document code in Documentá. 
Instead, I wanted to propose adding that documentation to Guile's 
documentation and link to it from Documentá. But I haven't made the time 
to write the proposed section.

Currently, Documentá can extract module documentation and procedure 
documentation. It also documents variables, record types, and macros 
exported by modules, but it simply lists them (record type fields are 
listed too), it doesn't extract any particular documentation added by 
human code writers. I haven't found, and in some cases investigated, a 
way to properly document variables, macros, record types and GOOPS 
clases using human-written documentation strings. But I want to have 
that too.

You can see examples of module and procedure documentation in 
Documentá's source 
(https://codeberg.org/luis-felipe/guile-documenta/src/branch/trunk/documenta). 
Note that for module documentation Documentá supports the conventional 
format

   ;;; Commentary:

   ;;; Your module documentation here ↓

   ;;; Code:

   ;;; Your code here ↓

Guile Scheme comments in the "Commentary" section are considered module 
documentation. You can use block comments too, the ones surrounded in #| 
... |#, instead of multiple line comments (see Documentá source code for 
examples).

Finally, better structuring, indexing and linking of generated API 
documentation are planned. I also want to explore exporting to Org format.

Hope that helps,

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2024-04-26 15:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  7:05 Some issues with guile Nikolaos Chatzikonstantinou
2024-04-26 15:21 ` Luis Felipe [this message]
2024-04-27  7:28   ` Nikolaos Chatzikonstantinou
2024-04-27 20:32     ` Luis Felipe
2024-04-26 16:23 ` Dr. Arne Babenhauserheide
2024-04-26 20:39 ` Tomas Volf
2024-04-27  7:46   ` Nikolaos Chatzikonstantinou
2024-04-27 14:09     ` Dr. Arne Babenhauserheide
2024-04-27 17:35     ` Linas Vepstas
2024-04-27 20:24       ` Luis Felipe
2024-04-28  5:06       ` Nikolaos Chatzikonstantinou

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=e5d3d38a-4fb7-ae6f-8e4b-56fba5c26748@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=guile-user@gnu.org \
    --cc=nchatz314@gmail.com \
    /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).