I have just released 0.6.2 version of QtOctave.
It hasn’t got thread’s bug, tables and View/mode/Dock work ok in Qt4.3 and Qt4.2
You can download it from:
I have just released 0.6.2 version of QtOctave.
It hasn’t got thread’s bug, tables and View/mode/Dock work ok in Qt4.3 and Qt4.2
You can download it from:
He liberado la versión 0.6.2 que corrige el bug de los hilos. Añade algunas nuevas características como la posibilidad de añadir botones de selección de ficheros en los menús de usuario, el modo View/Mode/Dock ya funciona correctamente tanto en Qt4.1 como en Qt4.3 y se ha corregido un fallo en las tablas en la versión para Qt4.3 (y Qt4.2).
La podéis encontrar en:
New QtOctave version is available for download:
Pues eso, ya está lista la versión 0.6.1 de QtOctave. Debería ser mucho más estable que las versiones anteriores, pero, por si no lo es, agradecería vuestros comentarios.
I’m thinking about new QtOctave version. I think that new version will be in next week. We have fixed a lot of bugs and it’s more estable than previus versions.
Estoy planificando la nueva versión de QtOctave que supongo que estará lista para la próxima semana. Se han corregido ya bastantes bugs y espero que más estable que las versiones anteriores.
I have written some notas about: “How to you can write fast code in interprete languages”.
2007-09-01-writing-fast-code-using-interpreted-languajes.pdf
I have implemented Drag and Drop for QtOctave’s file navigator. It looks useful!
You can download this feature from:
svn checkout https://forja.rediris.es/svn/csl-qtoctave
He implementado el arrastrar y soltar en el navegador de archivos de QtOvtave. ¡Y hasta es útil!
La versión con esta característica la podéis descargar desde:
svn checkout https://forja.rediris.es/svn/csl-qtoctave
He escrito unas notas sobre cómo aumentar el rendimiento a la hora de programar en lenguajes interpretados.
2007-09-01-optimizando-el-codigo-en-lenguajes-interpretados.pdf
Espero que os sean útiles.
I have written some notas about: “How you can write fast code in interprete languages”.
I will translate it to english soon.
I have just finished my exams. I will have free time and I will work in project. (Maybe it was the last exam of my career).
Por fin he acabado los exámenes y tendré más tiempo para dedicarle al proyecto. Con suerte es el último examen de la carrera que hago
A key question would be whether it is possible to compile Octave’s language. Such a question may be difficult to answer. Octave is an interpreted languaje which has in addition the eval function. This function makes everything to be very complicated due to the fact that the argument chosen for eval cannot be always predicted by the compiler. For example:
a=input(“Input:”);
eval(a)
The compiler would not know how to compile the second line. A possible solution may be make the compiler to call Octave whenever it reads the function eval. However, this solution cannot be considered “the optimal” since the function eval remains hidden in many other functions managed by Octave.
On the other hand, there are many other situations in which the compiler could deduce the argument of eval, so as to be able to compile the code in its best. For example:
eval(“2+3″)
In this case the answer will be always 5.
Maybe the best solution would be not to use eval and just simply rewrite those functions that use it. Only an Octave code with such conditions would be compiled with an optimal performance.