Hello,

Can somebody tell me the differnce between a call of a ksh with the dot :

>. script.ksh

and the call without the dot:

>script.ksh

In my script I have writen a test for the number of parameters:
if [ $# -ne 0 ]
then echo 'Usage : '$0
exit 1
fi

as my script doesn't need any parameter

if I call like this:
>. script.ksh
$# =
$0 = -ksh
which is wrong
I can't do a correct test of my parameters, but if I remove the parameter test I can give value to variables, and these variables are known and have a value in my parent shell and can be used by other scripts

If I call like this:
>script.ksh
$# = 0
$0 = script.ksh
which is OK, but I want to export variables that must be used in other script and my variables remains unknown in my parent shell
but it seems that I can execute other script that can see the variables....

I don't understand anything....

see you
Cécile

The difference is

$> . script.ksh

script.ksh is run in the current shell environment.

$> script.ksh

script.ksh is run in a new shell

If you script doesn't take any parameters then you don't need to explicitly check for it do you?

If you have defined functions in "script A" for example and you want them available to "script B" you could call "script A" inside "script B" with ". script A"