unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Bruce Korb <bkorb@veritas.com>
Cc: guile development <guile-devel@gnu.org>
Subject: Re: [PATCH] for strports.c: scm_c_eval_string_from_file_line
Date: Sun, 01 Jun 2003 13:38:22 -0700	[thread overview]
Message-ID: <3EDA643E.2215A945@veritas.com> (raw)
In-Reply-To: 87el2dlg9s.fsf@zagadka.ping.de

Marius Vollmer wrote:

>   void
>   scm_c_primitive_load_from_string (const char *str,
>                                     const char *filename, int line)
>   {
>     SCM port, exp;
> 
>     port = scm_open_input_string (scm_str2string (str));
>     scm_set_port_file_name_x (port, scm_str2string (filename));
>     scm_set_port_line_x (port, scm_int2num (line));
> 
>     while (!SCM_EOF_OBJECT_P (exp = scm_read (port)))
>       scm_primitive_eval_x (exp);
>   }
> 
> I think this quite straightforward, no?

No.

> But we might want to offer it ready-made, anyway.  Opinions?

Yes.  It is pretty close to what I wound up with, but I don't
track the preferred way to do things.  For Guile 1.4,
``scm_primitive_eval_x'' gets #define-d into ``scm_eval_x''
and it works.  I also try to avoid gratuitous creations of
string SCM's since the file name is generally invariant.
You omitted returning the final value, which is important :-).
It's easier to ignore if the caller doesn't want it.  And, no,
I didn't find that the research required to do this was obvious.
In fact, there is no ``scm_set_port_file_name_x'' in 1.6.3, so
you must be talking 1.7 here.  I'm still working with 1.4.
Therefore, I must directly assign to ``file_name''.  I may as
well assign the line number, too.

I'd rather it was ready made so I can just #define
my ``ag_scm_c_eval_string_from_file_line'' into
``scm_c_primitive_load_from_string''.  You might tweak it
a bit so a NULL file pointer bypasses the scm_set_port_file_name_x
call.  I'd also use "file_line" in the name, but that is your call.


EXPORT SCM
ag_scm_c_eval_string_from_file_line( tCC* pzExpr, tCC* pzFile, int line )
{
    SCM port;

    {
        tSCC zEx[] = "eval-string-from-file-line";
        SCM  expr  = scm_makfrom0str( pzExpr );
        port = scm_mkstrport( SCM_INUM0, expr, SCM_OPN | SCM_RDNG, zEx );
    }

    {
        static SCM file = SCM_UNDEFINED;
        scm_t_port* pt;

        if (  (file == SCM_UNDEFINED)
           || (strcmp( SCM_CHARS( file ), pzFile ) != 0) )
            file = scm_makfrom0str( pzFile );

        pt = SCM_PTAB_ENTRY( port );
        pt->line_number = line - 1;
        pt->file_name   = file;
    }

    {
        SCM ans = SCM_UNSPECIFIED;

        for (;;) {
            SCM form = scm_read( port );
            if (SCM_EOF_OBJECT_P( form ))
                break;
            ans = scm_primitive_eval_x( form );
        }

        return ans; // return the last answer
    }
}


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-06-01 20:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-24 20:47 [PATCH] for strports.c: scm_c_eval_string_from_file_line Bruce Korb
2003-06-01 20:00 ` Marius Vollmer
2003-06-01 20:38   ` Bruce Korb [this message]
2003-06-09 19:53     ` Marius Vollmer

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=3EDA643E.2215A945@veritas.com \
    --to=bkorb@veritas.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).