From: Bruce Korb <bkorb@veritas.com>
Cc: guile development <guile-devel@gnu.org>
Subject: Re: How do I determine the argument type...
Date: Sat, 17 May 2003 19:59:05 -0700 [thread overview]
Message-ID: <3EC6F6F9.EAF89167@veritas.com> (raw)
In-Reply-To: 87of213tk0.fsf@zagadka.ping.de
Marius Vollmer wrote:
> Ahh, I see. Yes, it was not a good thing to change gh_new2str that
> way. I'm not sure what to do about this. Changing this back is just
> as bad as the original change from int to size_t.
Right. So, what to do now is set up a config macro that
puts an scm2newstr_size_t into config.h and provide it for your
clients (e.g. me).
> Personally, I would stop supporting Guile 1.4 and just require Guile
> 1.6 for newer versions of your code...
Not a good choice until 1.4 becomes fairly rare. A few more years yet.
Heck, some people still sweat K&R compilers and functionless shells!
> I dirty workaround, in this particular case, might be to always pass
> NULL as lenp and get the length via scm_string_length
I thought of that and, in the end, I devised a way to avoid the
offending calls. The code is tighter now. :-)
But, the truth is, this is just an annoyance problem. I would _really_
like to fix the error messages emitted by libguile without having to
read source code to figure out how to rewrite gh_eval_str to be able
to plug in a file name and line number. I've actually made a couple
of runs at it, but I confess to finding the code a bit difficult to
follow..... :-(
Regards,
Bruce
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-18 2:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 3:27 How do I determine the argument type Bruce Korb
2003-05-10 3:31 ` Bruce Korb
2003-05-17 20:14 ` Marius Vollmer
2003-05-17 21:16 ` Bruce Korb
2003-05-18 1:57 ` Marius Vollmer
2003-05-18 2:59 ` Bruce Korb [this message]
2003-05-19 0:07 ` Kevin Ryde
2003-05-19 0:34 ` Bruce Korb
2003-05-19 0:47 ` Kevin Ryde
2003-05-19 1:44 ` Bruce Korb
2003-06-01 18:45 ` Marius Vollmer
2003-06-01 20:07 ` Bruce Korb
2003-06-11 22:33 ` Kevin Ryde
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=3EC6F6F9.EAF89167@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).