unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org, David Pirotte <david@altosw.be>
Subject: Re: Problems with guile-sqlite3
Date: Mon, 04 Apr 2011 23:28:39 +0200	[thread overview]
Message-ID: <m2oc4lbta0.fsf@ohwell.denx.de> (raw)
In-Reply-To: <m34o6du4fa.fsf@unquote.localdomain> (Andy Wingo's message of "Mon, 04 Apr 2011 22:50:33 +0200")

Hi Andy,

> On Mon 04 Apr 2011 18:22, Detlev Zundel <dzu@denx.de> writes:
>
>>> I spotted where the problem comes from: it is when a text value is empty. I have
>>> produced a small but complete example [attached]: can you reproduce it ?
>>
>> Yes, thanks for the test case, I can now reproduce it and hopefully the
>> attached patches work for you also.
>
> I have added you to the gitorious repo.  Feel free to push your patches
> there :-)

Hey thanks!  Still I'd welcome if you at least look over my changes and
give me some hints if you see room for improvements - most of what I did
in scheme in the past was in scsh ;)

As I said in my previous mail, I'd like to know if there is a better way
to handle the null pinter problem reported by Dave, e.g. does guile have
a null-pointer? or something comparable more gentle on the eyes than (eq
%null-pointer ..)?  If not, would it make sens to add such a predicate?

Thanks
  Detlev

-- 
Once the  implementation is  up and running,  it is still a trick to keep it
running.  In a normal,  closed implementation,  this is not a problem;  in a
system with metaobject protocols [..] there is the potential for spectacular
failure modes if certain situations are not properly anticipated.
                                       -- The Art of the Metaobject Protocol
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de



  reply	other threads:[~2011-04-04 21:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 22:52 Problems with guile-sqlite3 Detlev Zundel
2011-03-31 10:25 ` Andy Wingo
2011-03-31 14:03   ` Detlev Zundel
2011-03-31 16:18     ` Detlev Zundel
2011-04-01  5:33       ` David Pirotte
2011-04-01  9:12         ` Detlev Zundel
2011-04-01 23:05           ` David Pirotte
2011-04-04 16:22             ` Detlev Zundel
2011-04-04 20:50               ` Andy Wingo
2011-04-04 21:28                 ` Detlev Zundel [this message]
2011-04-11 15:05                   ` Detlev Zundel
2011-04-20 15:22               ` David Pirotte
2011-04-20 15:51                 ` Detlev Zundel
2011-04-21 12:17                   ` Andy Wingo
2011-04-21 21:58                     ` David Pirotte
2011-04-01 11:34       ` Andy Wingo
2011-04-01 14:33         ` Detlev Zundel
2011-04-01 14:49           ` Andy Wingo
2011-03-31 14:28   ` Ludovic Courtès
2011-03-31 14:54     ` Andy Wingo

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=m2oc4lbta0.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --cc=david@altosw.be \
    --cc=guile-devel@gnu.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).