Creating blocks there is really difficult. Stick exactly to the recipe
provided by the skeletons, and don't forget to build for new blocks.
After that, load the toolbox.
The underlying functions can be updated in Scilab memory by executing
the definition file, after the toolbox is loaded for quick test
iterations (of course, the built package won't be updated).
Thanks a lot! I could not load the website linked.
Can you please tell where are the BLOCKNAME.sci files located for the
built-in blocks? I could only find the .c files in the
Concretely, I'm interested in the formal semantics of the blocks, if they're
available. If they're not available, I'd like to analyze the blocks' source
code, to (automatically) find pre/post conditions for the blocks, for
instance. If you're already doing this, or aware of any such work, it'd be
great if you could point me to it!
The directly called code for every module is in the macros subfolder of
the module. Also stated in the Help.
As for mnotation, These Macros return siome scicos block, that containd
everything. Insiode you get the required model with scicos_model, which
contains all the Executables, parameters, IO sizes,... for the block.
The build in bloxks/askeleton shows easily enough, what you need there.
Just keep stuff consistent.
And that Link worked for me. I checked it before sending it.