I have a macro that is both windows/linux compatible.
I use stuff like
static _str COMMAND;
COMMAND = "bin_dir"FILESEP"executable_name"EXTENSION_EXE;
Now, all worked perfectly OK, except when I gave these macros to my co-worker which have a linux machine,
it still gave him a bad COMMAND (with '/' and 'exe').
Another weird thing is when I open the .e file on the linux SE and point the mouse to FILESEP I see the correct one!
Can anyone try to explain to me why I see windows stuff on the COMMAND str?