unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: Bruce Korb <bruce.korb@gmail.com>,
	guile-devel Development <guile-devel@gnu.org>
Subject: Re: unknown location: definition in expression context in subform optname-from of "_^"
Date: Wed, 25 Jan 2012 20:22:26 -0800 (PST)	[thread overview]
Message-ID: <1327551746.85660.YahooMailNeo@web37907.mail.mud.yahoo.com> (raw)
In-Reply-To: <4F20CEE7.4000403@gmail.com>

> From: Bruce Korb <bruce.korb@gmail.com>

>>  unknown location: definition in expression context in subform optname-from 
> of "_^"
>>  Scheme evaluation error.  AutoGen ABEND-ing in template
>>          /old-home/ROOT/usr/local/share/autogen/aginfo.tpl on line 163
>>  Failing Guile command:  = = = = =
>> 
>>  (define opt-name       "")
>>  (define extra-ct       0)
>>  (define extra-text     "")
>>  (define optname-from   "A-Z_^")  ;;<<<=== is something 
> wrong here?  What, exactly?
>>  (define optname-to     "a-z--")
>>  (make-tmp-dir)
> 
> what is the message trying to say?

For some reason, it thinks that you're not at the top level, but
instead in the middle of some expression.

It might be saying that you've missed a close parenthesis
on a define somewhere above.  The following would give the same error:

(define (func x) 
   (1+ 
    (define optname-from "A-Z_^"))

But if that were true, you'd expect it to bork on one of the other
lines in your code snippet as well.

You could try having EMACS re-indent the whole buffer to see if you
slipped a paren.  Otherwise, I don't know.

-Mike




  reply	other threads:[~2012-01-26  4:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26  3:56 unknown location: definition in expression context in subform optname-from of "_^" Bruce Korb
2012-01-26  4:22 ` Mike Gran [this message]
2012-01-26  5:31   ` David Kastrup
2012-01-26 21:05   ` Bruce Korb
2012-01-26 21:21     ` Mike Gran
2012-01-26 21:37       ` Bruce Korb
2012-01-27  0:10     ` Mark H Weaver
2012-01-27  0:56       ` Bruce Korb
2012-01-27  2:26         ` Mark H Weaver
2012-01-27  2:44           ` Bruce Korb
2012-01-27  2:59             ` Noah Lavine
2012-01-27  3:36               ` Bruce Korb
2012-01-28  7:02                 ` Mark H Weaver
2012-01-28 16:58                   ` Bruce Korb
2012-01-28 19:03                     ` Andy Wingo
2012-01-28 19:47                       ` Mark H Weaver
2012-01-28 22:58                         ` Andy Wingo
2012-01-29  4:12                           ` Mark H Weaver
2012-01-29 17:40                             ` Bruce Korb
2012-01-29 18:06                               ` Mike Gran
2012-01-29 20:28                             ` Andy Wingo
2012-01-29 21:14                               ` Bruce Korb
2012-01-29 21:32                               ` Mark H Weaver
2012-01-28 22:59                         ` Andy Wingo
2012-01-27  6:27               ` Mark H Weaver
2012-01-27  6:19             ` Mark H Weaver
2012-01-27 14:04               ` Bruce Korb
2012-01-27 14:32                 ` Mark H Weaver

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=1327551746.85660.YahooMailNeo@web37907.mail.mud.yahoo.com \
    --to=spk121@yahoo.com \
    --cc=bruce.korb@gmail.com \
    --cc=guile-devel@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).