Différences

Ci-dessous, les différences entre deux révisions de la page.

--- start:overrides [2026/03/26 16:08] – [Tracking patches and customscriptings needs in plugin design] admin
+++ start:overrides [2026/03/26 16:08] (Version actuelle) – [Tracking patches and customscriptings needs in plugin design] admin
@@ Ligne 93: / Ligne 93: @@
 So it may be possible that assembling several unrelated plugins might need to overload the same core files.
-In case of patchs, all patchs are bounded strictly in ''<nowiki>//</no<iki> PATCH+'' and ''<nowiki>//</no<iki> PATCH-'' comments, so they are easy to locate in the code. In the future, we will have to make some effort in generalizing the @see tag so each patch refers to the plugin that required it.
+In case of patchs, all patchs are bounded strictly in ''<nowiki>//</nowiki> PATCH+'' and ''<nowiki>//</nowiki> PATCH-'' comments, so they are easy to locate in the code. In the future, we will have to make some effort in generalizing the @see tag so each patch refers to the plugin that required it.
-In case of customscripts, the case of collision is also possible. In most case we try to use ''<nowiki>//</no<iki> CHANGE +'' and ''<nowiki>//</no<iki> CHANGE-'' comments to locate them.
+In case of customscripts, the case of collision is also possible. In most case we try to use ''<nowiki>//</nowiki> CHANGE +'' and ''<nowiki>//</nowiki> CHANGE-'' comments to locate them.
 [[:start|Back to general index]]