From: dpb on
Andy wrote:
> I should also point out that this behavior acts "appropriately" if the
> function happens to return a structure:
>
> % in a separate m-file
> function a=myFunction
> a.f1=3;
> a.f2=5;
> end
>
>
> % at the command line
>>> myFunction.f1
> ans =
> 3
>
> But I have to say I think I would rather this return an error. This
> seems like it could lead to eval-like, difficult-to-debug errors.

That seems sensible...but not quite the same as the ".m" call to execute
the function that looks like a structure reference syntactically...

--
From: Steven_Lord on


"Andy " <myfakeemailaddress(a)gmail.com> wrote in message
news:i2ui3o$3s7$1(a)fred.mathworks.com...
> I should also point out that this behavior acts "appropriately" if the
> function happens to return a structure:
>
> % in a separate m-file
> function a=myFunction
> a.f1=3;
> a.f2=5;
> end
>
>
> % at the command line
>>> myFunction.f1
> ans =
> 3
>
> But I have to say I think I would rather this return an error. This seems
> like it could lead to eval-like, difficult-to-debug errors.

Take a look at the Release Notes for MATLAB 7.10 (release R2010a):

http://www.mathworks.com/access/helpdesk/help/techdoc/rn/br_bpq8-1.html#br_bpq8-8

--
Steve Lord
slord(a)mathworks.com
comp.soft-sys.matlab (CSSM) FAQ: http://matlabwiki.mathworks.com/MATLAB_FAQ
To contact Technical Support use the Contact Us link on
http://www.mathworks.com