Comments on: More on eval http://blogs.mathworks.com/loren/2006/01/04/more-in-eval/ Loren Shure works on design of the MATLAB language at MathWorks. She writes here about once a week on MATLAB programming and related topics. Thu, 09 Feb 2012 04:19:21 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Loren http://blogs.mathworks.com/loren/2006/01/04/more-in-eval/#comment-30578 Loren Thu, 10 Sep 2009 10:54:23 +0000 http://blogs.mathworks.com/loren/?p=15#comment-30578 Hiroshi- I recommend using dynamic field names with structures. Here's an example: <pre class="code"> label = 'loren' d.([label] str2int(4) = data{4}; %% now there's a struct with field 'loren4' </pre> --Loren Hiroshi-

I recommend using dynamic field names with structures. Here’s an example:

label = 'loren'
d.([label] str2int(4) = data{4};
%% now there's a struct with field 'loren4'

–Loren

]]> By: Hiroshi Furutani http://blogs.mathworks.com/loren/2006/01/04/more-in-eval/#comment-30577 Hiroshi Furutani Thu, 10 Sep 2009 07:04:42 +0000 http://blogs.mathworks.com/loren/?p=15#comment-30577 Hi Loren, I understand why creating variable with dynamically-assigned name should be avoided. It will be very complex on Matlab. But I have to admit that variables with specific names are really useful to understand the content later and further data analysis. Just looking at the workspace, one can understand the content. Is there any better and practical way to make both sides happy? Hi Loren,
I understand why creating variable with dynamically-assigned name should be avoided. It will be very complex on Matlab. But I have to admit that variables with specific names are really useful to understand the content later and further data analysis. Just looking at the workspace, one can understand the content.

Is there any better and practical way to make both sides happy?

]]>