From gernot.eric at wanadoo.fr Fri May 3 20:56:24 2019 From: gernot.eric at wanadoo.fr (ericgernot) Date: Fri, 3 May 2019 11:56:24 -0700 (MST) Subject: [Scilab-Dev] New xcos blocks executing scilab primitive functions In-Reply-To: <1523018856774-0.post@n3.nabble.com> References: <1523018856774-0.post@n3.nabble.com> Message-ID: <1556909784995-0.post@n3.nabble.com> Hi guys, I have been out for a while, but reading this topic again raised a question: If I understand well, when the simulation starts, the Xcos engine creates all the blocks' structures, one for each block I guess, allocating memory for the block at this moment. But the Scilab engine can only work with numbers in its own memory allocation, right ? (I see it there: https://help.scilab.org/docs/6.0.2/en_US/DoubleManagement_callscilab.html) Or is it possible to have it directly operate on memory outside of it ? Reading the block structure definition, I may see a solution: "void **work; // Table of pointers to the block workspace (if allocation done by the block)". Which code has to be modified so that when the Sci_func block structure is created, the block is directly allocated a workspace made of pointers to Scilab memory? -- Sent from: http://mailinglists.scilab.org/Scilab-developers-Mailing-Lists-Archives-f2574944.html From gernot.eric at wanadoo.fr Fri May 3 20:56:47 2019 From: gernot.eric at wanadoo.fr (ericgernot) Date: Fri, 3 May 2019 11:56:47 -0700 (MST) Subject: [Scilab-Dev] New xcos blocks executing scilab primitive functions In-Reply-To: <1523018856774-0.post@n3.nabble.com> References: <1523018856774-0.post@n3.nabble.com> Message-ID: <1556909807964-0.post@n3.nabble.com> Hi guys, I have been out for a while, but reading this topic again raised a question: If I understand well, when the simulation starts, the Xcos engine creates all the blocks' structures, one for each block I guess, allocating memory for the block at this moment. But the Scilab engine can only work with numbers in its own memory allocation, right ? (I see it there: https://help.scilab.org/docs/6.0.2/en_US/DoubleManagement_callscilab.html) Or is it possible to have it directly operate on memory outside of it ? Reading the block structure definition, I may see a solution: "void **work; // Table of pointers to the block workspace (if allocation done by the block)". Which code has to be modified so that when the Sci_func block structure is created, the block is directly allocated a workspace made of pointers to Scilab memory? -- Sent from: http://mailinglists.scilab.org/Scilab-developers-Mailing-Lists-Archives-f2574944.html From sgougeon at free.fr Fri May 31 18:49:22 2019 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 31 May 2019 18:49:22 +0200 Subject: [Scilab-Dev] Processing the bug 14741: documenting [f, e]=log2() and masking frexp() Message-ID: Hello, Do we agree about processing the bug 14741 ? Any comment? Regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Fri May 31 18:57:29 2019 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 31 May 2019 18:57:29 +0200 Subject: [Scilab-Dev] tests: <-- ENGLISH IMPOSED --> removed and gettext() added: why? Message-ID: Hello, In some commits just before the release of 6.0.2, and more recently on the master, i noticed that when some tests are tagged with the <-- ENGLISH IMPOSED --> flag and some error messages are tested against their english version, without calling gettext, the reviewer removes the flag and adds gettext(). What's the reason for this? What's the purpose of the <-- ENGLISH IMPOSED --> flag, then ? Theoretically, the message in english can be different from the message_id (also in english). Is it the reason? Or what else? Thanks for your insight about this topic. Regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: