[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Handling "parfor" as "for"
From: |
Søren Hauberg |
Subject: |
Re: Handling "parfor" as "for" |
Date: |
Thu, 29 Sep 2011 09:08:13 +0200 |
tor, 29 09 2011 kl. 02:58 -0400, skrev John W. Eaton:
> Now Octave can accept statements of the form
>
> parfor LHS = EXPR BODY end
> parfor ( LHS = EXPR, MAXPROC ) BODY end
Does it have the corresponding 'end's ? I.e. can I write
parfor LHS = EXPR
BODY
endfor
or
parfor LHS = EXPR
BODY
endparfor
?
Søren
- Re: Handling "parfor" as "for", (continued)
- Re: Handling "parfor" as "for", John W. Eaton, 2011/09/26
- Re: Handling "parfor" as "for", Mark Everitt, 2011/09/26
- Re: Handling "parfor" as "for", Mark Everitt, 2011/09/27
- Re: Handling "parfor" as "for", Jordi Gutiérrez Hermoso, 2011/09/27
- Re: Handling "parfor" as "for", Mark Everitt, 2011/09/28
- Re: Handling "parfor" as "for", Jordi Gutiérrez Hermoso, 2011/09/29
- Re: Handling "parfor" as "for", Mark Everitt, 2011/09/29
- Re: Handling "parfor" as "for", John W. Eaton, 2011/09/29
- Re: Handling "parfor" as "for", Mark Everitt, 2011/09/29
- Re: Handling "parfor" as "for", John W. Eaton, 2011/09/29
- Re: Handling "parfor" as "for",
Søren Hauberg <=
- Re: Handling "parfor" as "for", John W. Eaton, 2011/09/29
- Re: Handling "parfor" as "for", John W. Eaton, 2011/09/29
- Re: Handling "parfor" as "for", Søren Hauberg, 2011/09/29
Re: Handling "parfor" as "for", Jussi Lehtola, 2011/09/26