Re: [Swig-devel] [MATLAB] Name conflicts when calling NewFile

[Joel A. <j.a...@gm...>]

Hello!

2014-05-22 8:34 GMT+02:00 William S Fulton <ws...@fu...>:

> On 19/04/14 19:14, Joel Andersson wrote:
>
>> Hello!
>>
>> In the MATLAB module I am working on I need to generate one .m file per
>> proxy proxy class and one .m file per global function. That means that I
>> may end up with two files with the same name (e.g. MyClass.m and
>> myclass.m) if there are two symbols that only differ in case.
>>
>>  Generating one file per global function is crazy. Why not put all the
> functions into one file? Have you looked at the other modules for ideas.
> The strongly typed languages use a 'module class' which is one class
> containing all the global functions.


I would say that this is a MATLAB syntax problem if anything. Until
recently, MATLAB required that every member function be defined in a
separate file (and one directory per class). They only recently added
support for multiple member function declarations in a single file, which
is what I use. For global functions, there is no corresponding possibility
(yet). Since a properly coded C/C++ project shouldn't define too many
global symbols, I didn't think of this as a big problem.


 When I generate the files using the NewFile command, the first generated
>> file gets overwritten instead of generating a second file alongside it.
>> Is this a bug?
>>
>>  No, using a caseless file system is a bug ;) Take a look at
> WARN_LANG_PORTABILITY_FILENAME. Anyone wanting to use a caseless file
> system will then no what to fix, assuming they read warnings.
>

Thanks!

Joel




-- 
-- 
Joel Andersson, PhD
Ptge. Busquets 11-13, atico 3
E-08940 Cornella de Llobregat, Spain
Home: +34-93-6034011
Mobile: +32-486-672874 (Belgium) / +34-63-4408800 (Spain) / +46-707-360512
(Sweden)