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
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
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 size and
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
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
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)
> |
> |
