From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Greg J. Badros" <gjb@cs.washington.edu>
To: Marius Vollmer <mvo@zagadka.ping.de>
Cc: Mikael Djurfeldt <mdj@mdj.nada.kth.se>, Ariel Rios <ariel@arcavia.com>, guile@sourceware.cygnus.com, guile-gtk@sourceware.cygnus.com, djurfeldt@nada.kth.se
Subject: Re: Patch to make guile-gtk work with upcoming guile-1.4
Date: Mon, 19 Jun 2000 15:01:00 -0000
Message-id: <qrr66r5uy8z.fsf@clavicle.cs.washington.edu>
References: <200006020301.WAA23978@erin.galway.com.mx> <qrr3dmawhl4.fsf@clavicle.cs.washington.edu> <xy766r69h0u.fsf@mdj.nada.kth.se> <87k8flfjyn.fsf@zagadka.ping.de>
X-SW-Source: 2000-q2/msg00057.html

Marius Vollmer <mvo@zagadka.ping.de> writes:

> Mikael Djurfeldt <mdj@mdj.nada.kth.se> writes:
> 
> > The `scm_make_smob_type_mfpe' function has not been mentioned in the
> > NEWS file because it might become deprecated in next release of Guile.
> 
> But smob.h says:
> 
>   /* These next two functions are the supported way to create new SMOB types.
> 
>      scm_make_smob_type is useful if there are no special smob functions
>        and the defaults work for mark,free,print,equal_p, or you want to use
>        scm_set_smob_{mark,free,print,equalp}, below.
> 
>      scm_make_smob_type_mfpe is ideal if you need to set one or more of
>        the special smob functions-- use NULL for when the default function 
>        is fine 
>   */
> 
> The comment should be updated, probably.

Or we should just decide not to depracate the _mfpe piece.  I think it's 
imprudent to require the separate and redundant calls to scm_set_smob_
when the common usage suggests the _mfpe interface that permits
eliminating those redundancies.

Greg