On Fri, Oct 23, 2009 at 12:19 PM, Jaroslav Hajek <high...@gmail.com> wrote:
> On Fri, Oct 23, 2009 at 12:09 PM, Michael Creel <michael.cr...@uab.es> wrote:
>> On Fri, Oct 23, 2009 at 12:00 PM, Jaroslav Hajek <high...@gmail.com> wrote:
>>> On Fri, Oct 23, 2009 at 11:52 AM, Michael Creel <michael.cr...@uab.es>
>>> wrote:
>>>> On Fri, Oct 23, 2009 at 11:23 AM, Jaroslav Hajek <high...@gmail.com> wrote:
>>>>> On Fri, Oct 23, 2009 at 11:21 AM, Michael Creel <michael.cr...@uab.es>
>>>>> wrote:
>>>>>> On Fri, Oct 23, 2009 at 10:57 AM, Jaroslav Hajek <high...@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> parcellfun works like cellfun, so this usage is incorrect. see help
>>>>>>> for cellfun.
>>>>>>> Also, for questions that concern exclusively OctaveForge functions,
>>>>>>> please use the OctaveForge mailing list.
>>>>>>>
>>>>>>> octave:1> a = parcellfun (2, @sin, {1, 2})
>>>>>>> parcellfun: 2/2 jobs done
>>>>>>> a =
>>>>>>>
>>>>>>> 0.84147 0.90930
>>>>>>>
>>>>>>
>>>>>> Thanks. Sorry about the mail list confusion. I'm getting
>>>>>> octave:1> a = parcellfun(2, @sin, {1,2})
>>>>>> parcellfun: 2/2 jobs done
>>>>>> warning: broken pipe -- some output may be lost
>>>>>>
>>>>>> At this point octave seems to hang indefinitely. I'm running 64 bit
>>>>>> Kubuntu 9.04. Octave is 3.3.50+ checked out yesterday.
>>>>>>
>>>>>> Michael
>>>>>>
>>>>>
>>>>> Do you use the SVN version of the general package? If not, do so.
>>>>>
>>>>> --
>>>>
>>>> I had been using the released general package, but I just made if from
>>>> SVN, and I get the same result.
>>>> Thanks, M.
>>>>
>>>
>>> I'm using the same (3.3.50+ just built) on OpenSUSE 11.0 without
>>> problems. Does __exit__ work as expected for you?
>>> Otherwise, I'm afraid you'll need to investigate for yourself what is wrong.
>>>
>>> --
>>> RNDr. Jaroslav Hajek
>>> computing expert & GNU Octave developer
>>> Aeronautical Research and Test Institute (VZLU)
>>> Prague, Czech Republic
>>> url: www.highegg.matfyz.cz
>>>
>>
>> I'm re-sending this due to a confusing quoted-text misformatting problem.
>>
>> If it type __exit__ from the octave prompt, I get dropped out to the
>> shell. That's the expected behavior, correct? A little more
>> experimentation shows that it works sometimes:
>>
>> octave:1> parcellfun(1, @sin, {1,2})
>> parcellfun: 2/2 jobs done
>> octave:2> [a] = parcellfun(1, @sin, {1,2})
>> parcellfun: 2/2 jobs done
>> a =
>>
>> 0.84147 0.90930
>>
>> octave:3> [a] = parcellfun(2, @sin, {1,2,3})
>> parcellfun: 3/3 jobs done
>> a =
>>
>> 0.84147 0.90930 0.14112
>>
>> octave:4> [a] = parcellfun(2, @sin, {1,2})
>> parcellfun: 2/2 jobs done
>> warning: broken pipe -- some output may be lost
>>
>> M.
>>
>
> Never happens for me. I just tried at least 20 times, even 100 times
> with a for loop. So I can hardly help you.
> One place that may generate this is the block at lines 254-258; if
> closing pipes by subprocesses fails. But I don't know why that should
> happen for you and not for me.
>
> --
> RNDr. Jaroslav Hajek
> computing expert & GNU Octave developer
> Aeronautical Research and Test Institute (VZLU)
> Prague, Czech Republic
> url: www.highegg.matfyz.cz
>
OK, thanks for clearing up the syntax for me. I don't have the
knowledge to investigate further.
Thanks, Michael
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
