User`s guide

R2008a
15-4
findResource Now Sets Properties According to Configuration
The findResource function now sets the properties on the object it creates according to
the configuration identified in the function call.
Compatibility Considerations
In past releases, findResource could use a configuration to identify a scheduler, but did
not apply the configuration settings to the scheduler object properties. If your code uses
separate statements to find an object then set properties, this still works, but is not
necessary any more.
parfor Syntax Has Single Usage
The parfor statement is now recognized only for parallel for-loops, not for loops over a
distributed range in parallel jobs.
Compatibility Considerations
In R2007b, the pre-existing form of parfor was replaced by for i = (drange), but
both forms of syntax were recognized in that release. Now parfor has only one context,
so parfor statements used in parallel jobs in code for versions prior to R2007a must be
modified to use for (drange).
Limitations
P-Code Scripts
You can call P-code script files from within a parfor-loop, but P-code script cannot
contain a parfor-loop.
sim Inside parfor-Loops
Running simulations in a parfor-loop with the sim command at the top level of the
loop is not allowed in this release. A sim command visible in a parfor-loop generates
an error, although you can call sim inside a function that is called from the loop. Be sure
that the various labs running simulations do not have the same working directory, as
interference can occur with the simulation data.