Allan Rae <[EMAIL PROTECTED]> writes:
| > The 3. is of course to not use lyxstring. However then we will have
| > some problems with different non-conforming string implementations.
| > and we need to investigate what each of them does that makes them
| > non-conforming.
|
| There are other reas
On 14 Mar 2000, Lars Gullik Bjønnes wrote:
> Allan Rae <[EMAIL PROTECTED]> writes:
>
> | No it's not quite what you were expecting from the subject.
> |
> | I have an almost compiling implementation that uses a new:
> | bool LyXFunc::Dispatch(int action, int size, char * buf)
> |
> | where
Allan Rae <[EMAIL PROTECTED]> writes:
| No it's not quite what you were expecting from the subject.
|
| I have an almost compiling implementation that uses a new:
| bool LyXFunc::Dispatch(int action, int size, char * buf)
|
| where size and buf are the memory buffer filled with the extern
No it's not quite what you were expecting from the subject.
I have an almost compiling implementation that uses a new:
bool LyXFunc::Dispatch(int action, int size, char * buf)
where size and buf are the memory buffer filled with the externalized data
to be passed to/from the new lyxfunc
