Nicholas Clark <[EMAIL PROTECTED]> writes: > >We're trying to make this an easy embedding API. Yes, and we are in danger of "premature optimization" of the _interface_. What we need to start with is a list of "what we need to know" - they may as well be separate parameters at this point - then we can decide how best to group them and provide wrapper(s) that call the zillion parameter version. If there turns out to be only one sensible wrapper then it can become _the_ interface. -- Nick Ing-Simmons <[EMAIL PROTECTED]> Via, but not speaking for: Texas Instruments Ltd.
- Re: Opcodes (was Re: The extern... Buddha Buck
- Re: Opcodes (was Re: The extern... Dan Sugalski
- Re: Opcodes (was Re: The extern... Chaim Frenkel
- Re: Opcodes (was Re: The extern... Dan Sugalski
- Re: Opcodes (was Re: The extern... Chaim Frenkel
- Re: Opcodes (was Re: The extern... Dan Sugalski
- Re: Opcodes (was Re: The extern... Buddha Buck
- Re: Opcodes (was Re: The extern... Dan Sugalski
- Re: The external interface for ... Chaim Frenkel
- Re: The external interface for the ... Nick Ing-Simmons
- Re: The external interface for the ... Nick Ing-Simmons
- Re: The external interface for ... Tim Bunce
- Re: The external interface for the parser piece Chaim Frenkel
- Re: The external interface for the parser piece Dan Sugalski
- Re: The external interface for the parser piece Steve Fink
- Re: The external interface for the parser piece Bryan C. Warnock
- Re: The external interface for the parser piece Dave Storrs
- Re: The external interface for the parser piece Dan Sugalski
- Re: The external interface for the parser piece Dave Storrs
- Re: The external interface for the parser pi... Dan Sugalski
- Re: The external interface for the parser piece Simon Cozens