unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: stack calibration
Date: Tue, 31 Mar 2009 23:47:34 +0100	[thread overview]
Message-ID: <87myb1nwc9.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m31vsepdha.fsf@pobox.com> (Andy Wingo's message of "Mon\, 30 Mar 2009 20\:39\:45 -0700")

Andy Wingo <wingo@pobox.com> writes:

> Hi Neil,

Hi Andy,

> On Mon 30 Mar 2009 13:43, Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> FWIW, I think this kind of incantation is really horrible. Ditto for
>> usage of "guile-tools ...". What kind of a scripting language is it
>> that needs to be bootstrapped by a different language?
>
> Dunno. While guile-tools should probably be written in Scheme, it
> doesn't bother me. The strange invocation stuff is just to get around
> posix's #! limitations -- it should be:
>
>   #!/usr/bin/env guile -e ....
>
> but we all know the problem with that.

Only one argument being portably supported?  (I _think_ that's the
problem, but I'm not so sure that I don't want to check that that's
what you mean!)

> As far as needing the -e clause, it's so we can (use-modules (scripts
> compile)) in addition to being able to run it as a script. Not that I
> use that feature, but it is interesting.

I don't use it either, and I don't think it's interesting enough to
justify the oddness of the incantation.  I can't think of a scenario
where it really makes sense to have a module and main program combined
in the same file.  If the module part isn't generally useful it
doesn't need to be written as a module.  If the module is generally
useful, it should be given a place in the proper module tree (i.e. not
scripts/...), and the script file should (use-modules ...) it.

On the other hand, I took a look again at guile-tools and remembered
why that _is_ useful.  (Basically the same argument as "git ...",
i.e. not dropping tens of executables into the system $PATH.)  So I
take back some of my "FWIW..." rant. :-)

>> I think you may be misunderstanding.  stack-limit-calibration.scm
>> should make precisely 0 difference on the "canonical build platform" -
>> which in practice means ia32 GNU/Linux.
>
> ia32 GNU/Linux is sometimes broken -- for example, build it with -O0,
> and things often don't work at all.

Good point.

> I think I explained my perspective as well as I can in the other mail --
> perhaps we can follow that part of the discussion there?

D'oh! :-)  OK, let's do that.

      Neil




  reply	other threads:[~2009-03-31 22:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 21:19 stack calibration Andy Wingo
2009-03-27 22:04 ` Mike Gran
2009-03-27 22:29   ` Julian Graham
2009-03-30 20:43 ` Neil Jerram
2009-03-31  3:39   ` Andy Wingo
2009-03-31 22:47     ` Neil Jerram [this message]
2009-04-03 17:44       ` Andy Wingo
2009-03-31 17:45   ` Greg Troxel
2009-04-17  9:35   ` Andy Wingo
2009-03-31 16:20 ` Ludovic Courtès
     [not found] <47B2A8DF.9070004@tammer.net>
     [not found] ` <87tzkd8bvz.fsf@gnu.org>
     [not found]   ` <87ejbh8ben.fsf@gnu.org>
     [not found]     ` <47B2D88F.1040505@tammer.net>
     [not found]       ` <87ir0tvx6e.fsf@inria.fr>
2008-02-13 20:40         ` stack overflow Neil Jerram
2008-02-14  8:48           ` Ludovic Courtès
2008-02-14 10:26             ` Mikael Djurfeldt
2008-02-14 11:25               ` Ludovic Courtès
2008-02-14 11:39                 ` Mikael Djurfeldt
2008-02-25 21:52                   ` Neil Jerram
2008-09-12 20:47                     ` Stack calibration Ludovic Courtès
2008-09-27 18:20                       ` Neil Jerram
2008-09-28 20:05                         ` Ludovic Courtès
2008-09-30 22:10                           ` Neil Jerram
2008-10-02  8:25                             ` Andy Wingo
2008-10-02  8:38                               ` Neil Jerram
2008-10-02 22:30                             ` Neil Jerram
2008-10-06 22:32                               ` Ludovic Courtès
2008-10-06 23:11                                 ` Neil Jerram
2008-10-09 22:53                                   ` Neil Jerram
2008-10-10 13:22                                     ` Greg Troxel
2008-10-10 18:04                                       ` Neil Jerram
2008-10-10 18:28                                         ` Greg Troxel
2008-10-10 18:41                                           ` Neil Jerram
2008-10-11 17:22                                     ` Ludovic Courtès
2008-10-12 15:59                                       ` Neil Jerram
2008-10-12 21:16                                         ` Neil Jerram
2008-10-13 21:37                                           ` Neil Jerram
2008-10-14  7:25                                           ` Ludovic Courtès
2008-10-17 20:49                                             ` Neil Jerram
2008-10-14  7:19                                         ` Ludovic Courtès
2008-09-28 20:07                         ` Ludovic Courtès
2008-09-30 22:11                           ` Neil Jerram

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=87myb1nwc9.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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).