addpath question

I have this code running 2010b 32 and 64 bit versions on two machines respectively.

pax300_top_level = cd;

eval(['addpath ',pax300_top_level,'/Ambient'])

It works perfectly on 64bit but I get the following error running it on my 32bit work pc.

Warning: Name is nonexistent or not a directory: C:\Documents. > In path at 110 In addpath at 87 Warning: Name is nonexistent or not a directory: and. > In path at 110 In addpath at 87 Warning: Name is nonexistent or not a directory: Settings\WSUadm\My. > In path at 110 In addpath at 87 Warning: Name is nonexistent or not a directory: Documents\Remus\CMAPS\c_mapss_2p0\Ambient. > In path at 110 In addpath at 87

Note:Its not a '/' or '\' issue.

Thanks, Remus

Answer 1

[Fangjun Jiang]

Maybe it's because there is a white space in the folder name, such as 'My Documents'?

By the way, why do you use eval()? You can use the addpath() function directly. Please try that.

Answer 2

[Grzegorz Knor]

Try in this way:

eval(['addpath(''',pax300_top_level,'/Ambient'')'])

It should work on two systems.

[Grzegorz Knor]

Fangjun Jiang suggestion's to not use the eval command is a better solution.

[Remus]

It's not my code and I dont't want to make any changes

[Kaustubha Govind]

Are you working in a directory with spaces in its path? Try moving to one that doesn't have spaces?

[Fangjun Jiang]

+1. I think you found the root cause of the problem. Using the command format instead of the function format of addpath, the white space in the pax300_top_level string will cause the problem. I was not 100% sure before reading your answer.

[Walter Roberson]

If you are not willing to make changes to the (broken) code, then your only alternative is to arrange things so that you are not in a directory that has a space in the name. If that, too, is something you do not want to do, then.... ummm, I guess in that case you would have to hand the problem back to your supervisor for resolution.

Answer 3

[Walter Roberson]

Don't use eval if it can be avoided. Just use

addpath([pax300_top_level, '/Ambient'])

The 32 bit machine happens to have a space in the current directory name, so a space is included in the string you are generating. When you eval() that, the space is taken as indicating the end of the argument. That's the sort of problem that eval() can cause.