Hello Philipp,
Le 07/12/2020 à 09:02, P M a écrit :
Please enlighten meon my PC the current situation is like this:
Scilab 6.1.0
Loading order 1:
- scicv
- IPCV
--> in console: help imread
--> img = imread(filename[,flag]) // hence the imread
function from scicv is found /
Please enlighten meon my PC the current situation is like this:
Scilab 6.1.0
Loading order 1:
- scicv
- IPCV
--> in console: help imread
--> img = imread(filename[,flag])// hence the imread function
from scicv is found / used (?)
---
Loading order 2:
- IPCV
- scicv
--> in
Hi Samuel,
Thanks for your details explanations and examples, they are really helpful.
Yes you're right, the functions loaded are base on what you have describe,
not depending on the order the modules being loaded. Thanks for pointing
this out.
Regards,
Chin Luh
On Sat, 5 Dec 2020 at 02:37,
Hello Chin Luh,
Le 04/12/2020 à 01:57, Chin Luh Tan a écrit :
Hi all,
Stephane, Thanks for the quick examples to illustrate this.
Claus, as shown by Stephane, this could be now by ourselves now from
our own modules. Stephane has illustrated a quick demo on this, while
the one I was testing
Hi all,
Stephane, Thanks for the quick examples to illustrate this.
Claus, as shown by Stephane, this could be now by ourselves now from our
own modules. Stephane has illustrated a quick demo on this, while the one I
was testing with is the copy of toolbox skeleton inside the Scilab contrib,
This is the way it works in scilab for libraries:
mkdir lib1
mputl("function y=foo(x);y=x;end","lib1/foo.sci")
genlib("lib1","lib1")
mkdir lib2
mputl("function y=foo(x);y=2*x;end","lib2/foo.sci")
genlib("lib2","lib2")
lib("lib1")
lib("lib2")
-> lib1.foo(1)
ans =
1.
--> lib2.foo(1)
On 03/12/2020 02:10, TanCL wrote:
Hi, my previous message seems like not able to get posted due to some reason,
just to add some comment on this, I think the functions with same name under
2 different modules could be possibly called by:
That is exactly how things are working in Ada:
Hi Tan
I agree. The proposal, is it something we can do ourselves now, or will
it require implementation into Scilab first? Thank you for resending.
/Claus
On 03-12-2020 02:10, TanCL wrote:
Hi, my previous message seems like not able to get posted due to some reason,
just to add some
Mh. Nice Idea.
Maybe something like this is already possible?
Install toolboxed but remove from autoloader.
So scilab starts without toolboxed from atoms.
The script includes than the command, which module shall be loaded.
Thanks for the idea...i will try this.
Philipp
Am Dienstag, 24.
Hi all
I imagine naming conflicts can occur across different ATOMS.
How about a change where one has to specify which ATOMS module you're
using when calling a function, such that both can coexist side-by-side ?
I'm thinking Pythonic here, like if you import for example numpy, you
can write
Dear developers,
as I have many scripts with "imread" I wonder if some time in the future
duplicate functions names from IPCV and SCICV are going to be
removed/changed.
It's kind of disturbing to have to use atomsInstall/atomsRemove when using
different scripts.
I think this was discussed
11 matches
Mail list logo
