From: Mike Gran <spk121@yahoo.com>
To: Bruce Korb <bruce.korb@gmail.com>, Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>,
"guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: unknown location: definition in expression context in subform optname-from of "_^"
Date: Sun, 29 Jan 2012 10:06:15 -0800 (PST) [thread overview]
Message-ID: <1327860375.17453.YahooMailNeo@web37907.mail.mud.yahoo.com> (raw)
In-Reply-To: <CAKRnqNKPWLJ30cELvxNt-Mx_yJsFuXnwGFfjza33gmePbKCmkA@mail.gmail.com>
> From: Bruce Korb <bruce.korb@gmail.com>
> On Sat, Jan 28, 2012 at 8:12 PM, Mark H Weaver <mhw@netris.org> wrote:
>> In short, this single function allows code to do the ideal thing
>> relatively painlessly. Typical usage might be something like this:
>>
>> SCM
>> my_eval (const char *string, const char *file_name,
>> long line, long column)
>> {
>> return scm_eval_string_from_file
>> (scm_from_locale_string (string), SCM_UNDEFINED,
>> scm_from_locale_string (file_name), line, column, 0);
>> }
>>
>> What do you think?
>
> I think it is what I've wanted for years. Thank you!!
> Any of these variations would make me happy.
FWIW, looking at Andy's C functions that call eval-string, they
seem simple enough. But I never would have come up with that on my own.
When I'm doing C, I tend to focus on C API.
I'm agnostic on whether there should be a new C function for this,
but, if there isn't, the code from
http://lists.gnu.org/archive/html/guile-devel/2011-03/msg00091.html
should make its way into the manual as a reminder that you can do
better than scm_c_eval_string.
Thanks,
Mike
next prev parent reply other threads:[~2012-01-29 18:06 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
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 [this message]
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=1327860375.17453.YahooMailNeo@web37907.mail.mud.yahoo.com \
--to=spk121@yahoo.com \
--cc=bruce.korb@gmail.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).