unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: Panicz Maciej Godek <godek.maciek@gmail.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: SLAYER announcement and help request for preparing a GNU package
Date: Mon, 06 May 2013 23:25:59 +0200	[thread overview]
Message-ID: <874nefpzq0.fsf@zigzag.favinet> (raw)
In-Reply-To: <CAMFYt2a+ENUSakCWVAids9fYCz4MPF6vW7JaAg87hj+V08BhuQ@mail.gmail.com> (Panicz Maciej Godek's message of "Mon, 6 May 2013 21:36:33 +0200")

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

() Panicz Maciej Godek <godek.maciek@gmail.com>
() Mon, 6 May 2013 21:36:33 +0200

   Thanks :) I see that there are a few persons with similar ideas, and
   I wonder how powerful we'd become if we managed to orchestrate our
   powers somehow, as TTN suggested

Orchestration is a nice concept.  It is the marshalling of separate
efforts in a parallel direction (towards the audience), moderated
individually, but w/ group awareness, by precise changes in timing and
pitch.  Cool.

For this, i strongly urge everyone who wants to jam[0] to provide
documentation.  That is the minimal requirement, the tuning of your
instrument so that it does not burn the ears of others seated beside
you.  So what if you don't have (the autotools) rhythm?  That can (and
must!) be cyclically attained.  To start, you gotta have the right Hz.

"But ttn, documentation is a pain to create and maintain!"

Well, yes.  For creation, i offer as riposte Guile-BAUX[1], which helps
me painlessly convert:

--8<---------------cut here---------------start------------->8---
  PRIMPROC
  (mix_allocate_channels, "allocated-channels", 1, 0, 0,
   (SCM numchans),
   doc: /***********
  Dynamically change the number of channels managed by
  the mixer to @var{numchans}.  If decreasing the number
  of channels, the upper channels are stopped.  Return the
  new number of allocated channels.  */)
  {
  #define FUNC_NAME s_mix_allocate_channels
    ASSERT_INTEGER (numchans, 1);
  
    RETURN_INT (Mix_AllocateChannels (C_LONG (numchans)));
  #undef FUNC_NAME
  }
--8<---------------cut here---------------end--------------->8---

and

--8<---------------cut here---------------start------------->8---
  ;; Return the exact truncation (rounding to zero) of @var{number}.
  ;; This is ``safer'' than simply @code{inexact->exact}
  ;; for some Guile versions.
  ;;
  ;; @example
  ;; (define scale 0.180281690140845)
  ;; (inexact->exact scale)
  ;;   @result{} 3247666210160131/18014398509481984 ; Guile 1.8.7
  ;;   @result{} 0                                  ; Guile 1.4.x
  ;; (exact-truncate scale)
  ;;   @result{} 0
  ;; @end example
  ;;
  (define (exact-truncate number)
    (inexact->exact (truncate number)))
--8<---------------cut here---------------end--------------->8---

into:
<http://www.gnu.org/software/guile-sdl/manual/html_node/Audio.html#index-allocated_002dchannels>
and
<http://www.gnu.org/software/guile-sdl/manual/html_node/Miscellaneous-Utilities.html#index-exact_002dtruncate>
respectively.

The nice thing (IMNSHO) is that Guile-BAUX is itself a nontrivial chunk
of Guile Scheme, nothing more, and furthermore takes pains to rise above
the cacaphony of Guile version-specific quirks.

Documentation maintenance, on the other hand, is a charge laid squarely
on the Author and the Author's discipline and astuteness.  You know what
to do; you know how to do it; what must be dredged from the void is the
will and the practice, the mind and the motion.  I wish you fortitude.

_________________________________________________________
[0] http://www.merriam-webster.com/dictionary/jam
    (as in "jam session")

[1] http://www.gnuvola.org/software/guile-baux/

-- 
Thien-Thi Nguyen
GPG key: 4C807502

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2013-05-06 21:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-04 21:54 SLAYER announcement and help request for preparing a GNU package Panicz Maciej Godek
2013-05-05  5:15 ` John Darrington
2013-05-05  6:55   ` Stjepan Horvat
2013-05-05  6:59   ` Panicz Maciej Godek
2013-05-05 18:48     ` Thien-Thi Nguyen
2013-05-05 19:42       ` Popularity (was Re: SLAYER announcement ...) Mike Gran
2013-05-05 20:04         ` Popularity Frank Terbeck
2013-05-05 22:12         ` Popularity (was Re: SLAYER announcement ...) Chris Vine
2013-05-06  3:25         ` Nala Ginrut
2013-05-07 12:20         ` Ludovic Courtès
2013-05-05 21:37       ` SLAYER announcement and help request for preparing a GNU package Panicz Maciej Godek
2013-05-06  8:06 ` Javier Sancho
2013-05-06 19:36   ` Panicz Maciej Godek
2013-05-06 21:25     ` Thien-Thi Nguyen [this message]
2013-05-07 22:50       ` Panicz Maciej Godek
2013-05-08  9:34         ` Thien-Thi Nguyen
2013-05-08 12:51           ` Panicz Maciej Godek
2013-05-08 13:37             ` Mark H Weaver
2013-05-08 15:15               ` Mike Gran
2013-05-08 21:44                 ` Panicz Maciej Godek
2013-05-09  6:50             ` Thien-Thi Nguyen
2013-05-08 21:56           ` Ludovic Courtès
2013-05-07  7:23     ` Javier Sancho
2013-05-07 22:00       ` Panicz Maciej Godek

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=874nefpzq0.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=godek.maciek@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).