At 05:24 PM 2/5/2001 -0200, Branden wrote: >I just expect consistency, e.g. nothing like sv_xyz, SvXYZ, SV_XYZ, SVt_XYZ >and I wonder what else there would be!!! (damn XS!) Heh. Don't worry--I've been bitten by that more often than I care to think about. (I hate dealing with hashes in XS, since I'm pretty much guaranteed a half-dozen nasty crashes somewhere during debugging, not to mention some memory leaks for a while) A though-out (hopefully well thought out, but I'll take what I can get) API for extensions is on the list of things to do. (If you want to take a shot at it do feel free--the PDD template is in the archives...) Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
- Re: Specifying vtable API in terms of macros? Edwin Steiner
- Re: Specifying vtable API in terms of macros? Branden
- Re: Specifying vtable API in terms of macros? Edwin Steiner
- Re: Specifying vtable API in terms of macros? Branden
- Re: Specifying vtable API in terms of macr... Edwin Steiner
- Re: Specifying vtable API in terms of... Branden
- PMC vs. SV*/AV*/... in the core (... Edwin Steiner
- Re: PMC vs. SV*/AV*/... in the co... Branden
- Re: PMC vs. SV*/AV*/... in the co... Dan Sugalski
- Re: PMC vs. SV*/AV*/... in the co... Branden
- Re: PMC vs. SV*/AV*/... in the co... Dan Sugalski
- Re: PMC vs. SV*/AV*/... in the co... Dan Sugalski
- Re: Specifying vtable API in terms of macros? Simon Cozens
- RE: Specifying vtable API in terms of macros? Garrett Goebel
- Re: Specifying vtable API in terms of macros? Branden
- Re: Specifying vtable API in terms of macros? Dan Sugalski
- RE: Specifying vtable API in terms of macros? Dan Sugalski