Hi,
Maybe someon is interested in some findings about the problem
with
Tcl_SetIntObj(Tcl_GetObjResult(interp), 1);
i just workd through the xotcl c code, and found indeed a potential
source for the problem (in the non-frequently used
XOTclOIsMixinMethod() call) and fixed it.
It is my
On 25.09.2006, at 11:40, Gustaf Neumann wrote:
When doing some tests, it shows that the version with
Tcl_NewIntObj() is measurable slower than the version with the
reused result object (no wonder) but as well slower than the
version with Tcl_ResetResult().
For the following test, i measured
Unix is not Unix as I see...
Please note this (interesting) document:
http://developers.sun.com/solaris/articles/event_completion.html
Mostly interesting, as there is now a very powerful and scalable
notification interface on both Solaris and Mac OSX (aka BSD)
Unixes. Windows has it as well,
We use Linux only, so it will not affect us but if using new API will
change the way the program works, how it will be possible to support
Solaris, Linux, Windows and MaxOSX at the same time?
Zoran Vasiljevic wrote:
Unix is not Unix as I see...
Please note this (interesting) document:
On 25.09.2006, at 21:42, Vlad Seryakov wrote:
We use Linux only, so it will not affect us but if using new API will
change the way the program works, how it will be possible to support
Solaris, Linux, Windows and MaxOSX at the same time?
The same way as it is possible to maintain Windows
On 9/25/06, Zoran Vasiljevic [EMAIL PROTECTED] wrote:
Unix is not Unix as I see...
Please note this (interesting) document:
http://developers.sun.com/solaris/articles/event_completion.html
Mostly interesting, as there is now a very powerful and scalable
notification interface on both
