unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Matt Wette <matt.wette@gmail.com>
To: Guile User Mailing List <guile-user@gnu.org>
Subject: Re: ffi-help: documentation
Date: Sun, 7 Jan 2018 13:21:28 -0800	[thread overview]
Message-ID: <744A431D-6D60-4C31-BA56-50F3DBDBECFE@gmail.com> (raw)
In-Reply-To: <87373hnz8g.fsf@gnuvola.org>


> On Jan 7, 2018, at 1:19 PM, Thien-Thi Nguyen <ttn@gnu.org> wrote:
> 
> 
> () Matt Wette <matt.wette@gmail.com>
> () Wed, 6 Dec 2017 18:46:59 -0800
> 
>   Currently, I'm working on documentation.  I like manuals that
>   start out with simple demos to show what's going on.  That is
>   my approach here.  Enjoy ...
> 
> Cool.  Examples are great.  I suggest only one tweak, small but
> pervasive, that would improve text output format readability
> (IMHO): add blank lines around environments and prior to
> non-trivial ‘@item’ lines.
> 
> For example, compare the original (at beginning):
> 
> | come from naming a set of C include files.  The nominal
> | method for use is to write a _ffi-module_ specification in a
> | file which includes a 'define-ffi-module' declaration and
> | then use the command 'guild compile-ffi' to convert this to
> | Guile Scheme.
> |      $ guild compile-ffi ffi/cairo.ffi
> |      wrote `ffi/cairo.scm'
> | Note that no C code is generated.  The hooks to access
> | C-coded functions in the Cairo library are provided in 100%
> | Guile Scheme.
> 
> with a revision that adds blank lines around the ‘@example’:
> 
> | come from naming a set of C include files.  The nominal
> | method for use is to write a _ffi-module_ specification in a
> | file which includes a 'define-ffi-module' declaration and
> | then use the command 'guild compile-ffi' to convert this to
> | Guile Scheme.
> |
> |      $ guild compile-ffi ffi/cairo.ffi
> |      wrote `ffi/cairo.scm'
> |
> | Note that no C code is generated.  The hooks to access
> | C-coded functions in the Cairo library are provided in 100%
> | Guile Scheme.
> 
> (NB: This excerpt was refilled, but that is besides the point.)
> I find the latter easier to jump in and out of (skim) visually.
> 
> For more mumblings on "blank lines" see:
> - http://www.gnuvola.org/u/2017/08/08h21.html
> - http://www.gnuvola.org/u/2017/05/17h22.html
> - http://www.gnuvola.org/u/2017/05/16h15.html
> 
> [cc trimmed]
> 
> -- 
> Thien-Thi Nguyen -----------------------------------------------
> (defun responsep (query)
>   (pcase (context query)
>     (`(technical ,ml) (correctp ml))
>     ...))                              748E A0E8 1CB8 A748 9BFA
> --------------------------------------- 6CE4 6703 2224 4C80 7502

Thanks.  I will take that into serious consideration.

Matt





      reply	other threads:[~2018-01-07 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 14:00 ffi-help: varargs Matt Wette
2017-12-07  2:46 ` ffi-help: documentation Matt Wette
2018-01-07 21:19   ` Thien-Thi Nguyen
2018-01-07 21:21     ` Matt Wette [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=744A431D-6D60-4C31-BA56-50F3DBDBECFE@gmail.com \
    --to=matt.wette@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).