John Levon <[EMAIL PROTECTED]> writes:
| On 13 Oct 2000, Lars Gullik Bjønnes wrote:
|
| >
| > We should make a way to ensure that LyXFunc are called with the
| > correct number of arguments and also that the arguments are of the
| > correct type. I think I have a nice solution for this...first we
| > change the LyXFunc::dispatch to a different type of arg...
| >
|
| I was trying to read the core code this weekend, and I got confused
| between the the two classes LyXFunc/LyXAction. What is their relation ?
| They seem very similar ...
LyXAction deals with lookup of LFUNS, LyXFunc deals with execution of
LFUNS.
| What are the plans for the lyxfunc redesign ? Can we encapsulate every
| function into a certain set of parameters, e.g.
|
| enum: LFUN_RANDOM,
| command: "buffer-random",
| staticstate: NeedBuffer etc.,
| dynamicstate: Disabled etc.,
| description: "Generates random number",
| KB mapping: etc.
| <however the C++ gurus represent the function prototype>
Not that much so far, but yes why not.
| Out of interest can people comment on the big picture you are planning on
| here ?
There are not huge changes planned... just changes so that dynamic
typechecking of parameters can be done.
Lgb
