unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: nalaginrut <nalaginrut@gmail.com>
To: "Diogo F.S.Ramos" <diogofsr@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Installing scheme only programs
Date: Fri, 11 Mar 2011 13:24:40 +0800	[thread overview]
Message-ID: <1299821080.2579.22.camel@Renee-desktop> (raw)
In-Reply-To: <20110311.015705.296722706338946665.diogofsr@gmail.com>

> >> > I wonder if there is a tool to, say, strip all comments from the
> >> > "binary", so it could be smaller. I guess such tool would not be that
> >> > hard to write, but I don't know.
> >> 
> >> I think it's not a big deal if you just want to get rid of comments.I
> >> always do it like this way:
> >> ======
> >> sed "/;.*/d" filename
> >> ======
> > 
> > Careful!  Guile now has the expression comment #;
> > That sed would be bad for something like   (list a #;b c)
> 
> Thank you for the 'sed' recipe.
> 
> Unfortunately, it's deleting whole lines like:
> 
>   (foo bar) ;;this line is gone
> 

Well, I think it's a personal code style problem. I'd like to write
comments for a new line. Maybe 'sed  "s: ;.*::g" filename' is better.
Note there should be a space before ";" in case you are using a "#;" as
dismich said. But I think we must design a perfectly safe method. 
Anyway, I think it's a big deal now. :-)

To dismich: I don't know there's a "#;" now. Thanks for warning. And I'd
like to know what the "#;" means. :-)

-- 
GNU Powered it
GPL Protected it
GOD Blessed it

HFG - NalaGinrut




  reply	other threads:[~2011-03-11  5:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10  6:50 Installing scheme only programs Diogo F. S. Ramos
2011-03-10  9:57 ` Tristan Colgate-McFarlane
2011-03-10 17:42   ` Diogo F. S. Ramos
2011-03-10 10:34 ` Thien-Thi Nguyen
2011-03-10 17:46   ` Diogo F. S. Ramos
2011-03-11  2:18     ` nalaginrut
2011-03-11  4:50       ` dsmich
2011-03-11  4:57         ` Diogo F. S. Ramos
2011-03-11  5:24           ` nalaginrut [this message]
2011-03-11  9:16     ` Thien-Thi Nguyen
2011-03-11 12:53   ` Ludovic Courtès
2011-03-13  0:59     ` Thien-Thi Nguyen

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=1299821080.2579.22.camel@Renee-desktop \
    --to=nalaginrut@gmail.com \
    --cc=diogofsr@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).