unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Matt Wette <mwette@alumni.caltech.edu>
To: Taylan Ulrich Bayirli/Kammer <taylanbayirli@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: syncase code issue 1.8.8 -> 2.0.11
Date: Thu, 18 Sep 2014 05:35:04 -0700	[thread overview]
Message-ID: <45C40687-D393-42A0-9DD8-4C4D1029B1F0@alumni.caltech.edu> (raw)
In-Reply-To: <87k351ut62.fsf@taylan.uni.cx>


On Sep 18, 2014, at 3:20 AM, Taylan Ulrich Bayirli/Kammer <taylanbayirli@gmail.com> wrote:
> 
> I see your code is doing things like
> 
> (format #t "~a\n" (define mt (make-tokiz "abc=def")))
> 
> The argument to `format' there is necessarily an "expression" in the
> grammar of Scheme.  Definitions like (define ...) are not a valid type
> of expression in Scheme.

yes, just debug that didn't matter - please disregard


> The only places you can use definitions are
> 
> - the top-level of a program/library
> 
> - the *beginning* of a "code body" like the body of a `lambda', the body
>  of a `let', etc. can have a sequence of definitions; the first
>  non-definition expression terminates that sequence
> 
> - when you have a (begin ...) form in a position where a definition
>  would otherwise be allowed, then the body of this begin may also start
>  with a series of definitions; again, the first non-definition
>  expression terminates this sequence

This is syntax-case.   Go check share/guile/2.0/boot-9/psyntax.scm for similar code.

Matt




  reply	other threads:[~2014-09-18 12:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18  1:18 syncase code issue 1.8.8 -> 2.0.11 Matt Wette
2014-09-18  7:49 ` Panicz Maciej Godek
2014-09-18 10:20 ` Taylan Ulrich Bayirli/Kammer
2014-09-18 12:35   ` Matt Wette [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-18 14:08 mwette
2014-09-19  3:54 ` Matt Wette

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=45C40687-D393-42A0-9DD8-4C4D1029B1F0@alumni.caltech.edu \
    --to=mwette@alumni.caltech.edu \
    --cc=guile-user@gnu.org \
    --cc=taylanbayirli@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).