Re: Some questions about wrapping types
Hi Stephen, xemac-beta,
On Thu, Nov 27, 2014 at 9:48 AM, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
Johann 'Myrkraverk' Oskarsson writes:
> And on that note, why is that the internal putprop callback is
> supposed to return 0 to throw a lisp error, but the remprop callback
> is supposed to return -1? Wouldn't it have been better to synchronize
> it? (This is from Fput and Fremprop in fns.c).
All types, not just types in modules, use these conventions. I don't
think it's worth changing at this late date.
But there are only a handful of lrecords who actually implement
properties: strings, extents, faces, glyphs, symbols, gtkobjects and
gtkboxed; in 21.4 at least. Of course there can be more types that do
this too.
Has that changed in 21.5 so everything can have properties?
Anyway, the question is really about lowering the barrier for new
module developers.
> I also just checked, and afaict, this has not changed in 21.5.
> Given how few modules are actually out there (mine may be the only
> one who does types) do you want to change it?
What do you mean by "type"? As I use the word, every lrecord/lcrecord
is a different type. Most modules do create specialized lrecords, and
aside from those there are currently over 100 different ones in the
enum of lrecord_types in core.
In this case, I mean an emodule that implements a type.
Have fun,
Johann
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta