From dd132328a192ac22f3e5469352f8a3f7ff007f87 Mon Sep 17 00:00:00 2001 From: Jean Privat Date: Wed, 21 Oct 2015 16:20:40 -0400 Subject: [PATCH] model: move-up `is_fictive` from MModule to MEntity Signed-off-by: Jean Privat --- src/model/mmodule.nit | 5 ----- src/model/model_base.nit | 6 ++++++ 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/src/model/mmodule.nit b/src/model/mmodule.nit index db4b8c6..fdfe399 100644 --- a/src/model/mmodule.nit +++ b/src/model/mmodule.nit @@ -237,11 +237,6 @@ class MModule end end - # Is `self` created for internal purpose? - # Fictive modules are instantiated internally but they should not be - # exposed to the final user. - var is_fictive: Bool = false is writable - # Is `self` a unit test module used by `nitunit`? var is_test_suite: Bool = false is writable diff --git a/src/model/model_base.nit b/src/model/model_base.nit index a97ede8..2d2dfa0 100644 --- a/src/model/model_base.nit +++ b/src/model/model_base.nit @@ -79,6 +79,12 @@ abstract class MEntity # Note that the broken status is not propagated to enclosing and enclosed entities. # e.g. a broken method does not make the whole module broken. var is_broken = false is writable + + # Is `self` created for internal purpose? + # + # Fictive entities are used internally but they should not be + # exposed to the final user. + var is_fictive: Bool = false is writable end # Something that represents a concern -- 1.7.9.5