modelize_class: make the class-name-conflict a warning
authorJean Privat <jean@pryen.org>
Fri, 3 Apr 2015 02:44:12 +0000 (09:44 +0700)
committerJean Privat <jean@pryen.org>
Fri, 3 Apr 2015 06:09:35 +0000 (13:09 +0700)
as an error, it prevents temporary duplication of same classes
for development and experimentation.

One do not want to have an hard error in a file because a random file
in the same directory has issues.

Signed-off-by: Jean Privat <jean@pryen.org>

src/modelize/modelize_class.nit

index 632db85..5618c11 100644 (file)
@@ -105,7 +105,7 @@ redef class ModelBuilder
                                        if other.intro_mmodule.mgroup != null and other.intro_mmodule.mgroup.mproject == mmodule.mgroup.mproject then
                                                # Skip classes that are buggy
                                                if other.try_intro == null then continue
-                                               error(nclassdef, "Error: A class named `{other.full_name}` is already defined in module `{other.intro_mmodule}` at {other.intro.location}.")
+                                               warning(nclassdef, "full-name-conflict", "Error: A class named `{other.full_name}` is already defined in module `{other.intro_mmodule}` at {other.intro.location}.")
                                                break
                                        end
                                end