Re: Is fork() broken in octave 5.1 ?

[Kay Nick]

ftest.m :
function ret=ftest()
  [pid, msg]=fork();
  if (pid > 0)
    pid
    msg
  endif
  ret=0;


forktest.m
A=23;
ftest()

gives me

>> forktest
pid =  3345
msg =
ans = ans0
 = 0
>>

which is pretty much what I'd expect. Maybe we should mention this in
the documentation or in the error message... (only allowed in a function)

> The error message says "command line", but includes scripts as well.
> This error was added intentionally, so it looks to me like the function
> is working correctly.
Nevertheless I find this behavior not intuitive... What is the reason
for preventing fork() from being used in a simple script?

Marcin


On 26.09.19 19:04, Mike Miller wrote:
> On Thu, Sep 26, 2019 at 17:37:13 +0200, Kay Nick wrote:
>> ...or am I getting something wrong here?
>>
>> Dear folks,
>>
>> this simple script (forktest.m)
>>
>> A=23;
>> [pid, msg]=fork();
>> if (pid > 0)
>>   pid
>>   msg
>> endif
>>
>> gives me the error
>>
>>>> forktest
>> error: fork: cannot be called from command line
>> error: called from
>>     forktest at line 2 column 11
>>
>> Tested it on Arch Linux as well as Manjaro (64 bit) with all recent
>> updates installed. Any idea?
> The error message says "command line", but includes scripts as well.
> This error was added intentionally, so it looks to me like the function
> is working correctly. Have you tried turning forktest.m into a function
> file?
>