From: Bruce Korb <bkorb@gnu.org>
Subject: Re: No way out.
Date: Sun, 4 Dec 2005 20:08:00 -0800 [thread overview]
Message-ID: <200512042008.00333.bkorb@gnu.org> (raw)
In-Reply-To: <87lkz5mysf.fsf@zip.com.au>
On Wednesday 30 November 2005 04:44 pm, Kevin Ryde wrote:
> Collateral damage from the change to scm_inexact_p (other message).
> Not sure how one or both ought to work.
All *_p functions ought to accept anything without throwing an error.
Even if it doesn't seem to make sense. That way, I know I don't have
to validate before calling a validation routine. :-}
Anyway, *real bugs* in Guile 1.7.2 are:
1. When an error is thrown, "exit" should be called with EXIT_FAILURE, not 0.
2. After these commands:
(use-modules (ice-9 stack-catch))
(debug-enable 'backtrace)
I should be getting stack traces on Scheme errors. I'm not.
(And, yes, I invoke either ``(backtrace)'' or ``scm_backtrace()''
when a failure is detected.)
3. Either of these two implementations:
port = scm_open_input_string( AG_SCM_STR02SCM( pzExpr ));
#if GUILE_VERSION < 107000
{
static SCM file = SCM_UNDEFINED;
static char* pzFl = NULL;
scm_t_port* pt;
if ( (pzFl == NULL)
|| (strcmp( AG_SCM_CHARS( file ), pzFile ) != 0) ) {
if (pzFl != NULL)
free(pzFl);
pzFl = strdup( pzFile );
file = AG_SCM_STR02SCM( pzFile );
}
pt = SCM_PTAB_ENTRY(port);
pt->line_number = line - 1;
pt->file_name = file;
}
#else
{
static SCM file = SCM_UNDEFINED;
static char* pzOldFile = NULL;
if ((pzOldFile == NULL) || (strcmp( pzOldFile, pzFile ) != 0)) {
if (pzOldFile != NULL)
free( pzOldFile );
pzOldFile = strdup( pzFile );
file = scm_from_locale_string( pzFile );
}
scm_set_port_filename_x( port, file );
}
{
SCM ln = scm_from_int( line );
scm_set_port_line_x( port, ln );
}
#endif
should be enabling file and line numbers in errors. I've tried both methods
with 1.7 (and some others suggested in the discussion), to no avail. I can
get file and line information for 1.6.7 and earlier *only*. There seems to
be no way to do it in 1.7.
Thanks for your help! Regards, Bruce
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-12-05 4:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 0:16 gh_inexact_p error in 1.7.x Bruce Korb
2005-12-01 0:44 ` Kevin Ryde
2005-12-05 4:08 ` Bruce Korb [this message]
2005-12-05 4:35 ` No way out Bruce Korb
2005-12-07 1:31 ` Marius Vollmer
2005-12-05 22:20 ` Kevin Ryde
2005-12-06 10:58 ` Han-Wen Nienhuys
2005-12-28 15:59 ` Neil Jerram
2005-12-31 15:09 ` Han-Wen Nienhuys
2005-12-31 15:14 ` Neil Jerram
2006-01-01 19:58 ` Han-Wen Nienhuys
2006-01-02 15:42 ` Neil Jerram
2006-01-02 18:54 ` Neil Jerram
2006-01-04 21:13 ` Backtrace and enhanced catch Neil Jerram
2006-01-14 12:41 ` Neil Jerram
2006-01-22 13:47 ` Marius Vollmer
2006-01-23 20:11 ` Neil Jerram
2006-01-24 21:34 ` Marius Vollmer
2006-01-16 8:38 ` Ludovic Courtès
2006-01-18 23:08 ` Neil Jerram
2006-01-19 9:38 ` Ludovic Courtès
2006-01-21 11:26 ` Neil Jerram
2006-01-26 23:29 ` Kevin Ryde
2006-01-27 19:30 ` Neil Jerram
2006-01-31 20:07 ` Kevin Ryde
2006-02-01 23:04 ` Neil Jerram
2006-02-04 0:46 ` Kevin Ryde
2006-02-04 15:41 ` Neil Jerram
2005-12-07 1:07 ` No way out Marius Vollmer
2005-12-07 1:55 ` Rob Browning
2005-12-13 20:32 ` Marius Vollmer
2005-12-28 16:09 ` Neil Jerram
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=200512042008.00333.bkorb@gnu.org \
--to=bkorb@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).