JADE (programming language): Difference between revisions

Line 21:

Like all of the other popular programming languages used to create database-driven software, JADE is fully [[object-oriented programming|object-oriented]]. JADE was designed to have all the most important features of object-oriented programming, but does not support the overloading of methods or operators, and until Jade 2018 lacked parameterised constructors.<ref name="obscure"/>

Classes in JADE are kept together in [[logical schema|schemas]]. Schemas serve the same purpose as [[Java package]]s or [[namespaces]] in .NET, but have a hierarchy, and inherit classes from superschemas. This becomes useful especially when programming using the [[~~model-view-controller~~]] methodology, as model classes can be put in one schema, then the controller and view classes can be built on top of the model classes in a subschema.

Classes in JADE are kept together in [[logical schema|schemas]]. Schemas serve the same purpose as [[Java package]]s or [[namespaces]] in .NET, but have a hierarchy, and inherit classes from superschemas. This becomes useful especially when programming using the [[model–view–controller]] methodology, as model classes can be put in one schema, then the controller and view classes can be built on top of the model classes in a subschema.

===Program structure===

@@ Line 21: / Line 21: @@
 Like all of the other popular programming languages used to create database-driven software, JADE is fully [[object-oriented programming|object-oriented]]. JADE was designed to have all the most important features of object-oriented programming, but does not support the overloading of methods or operators, and until Jade 2018 lacked parameterised constructors.<ref name="obscure"/>
-Classes in JADE are kept together in [[logical schema|schemas]]. Schemas serve the same purpose as [[Java package]]s or [[namespaces]] in .NET, but have a hierarchy, and inherit classes from superschemas. This becomes useful especially when programming using the [[model-view-controller]] methodology, as model classes can be put in one schema, then the controller and view classes can be built on top of the model classes in a subschema.
+Classes in JADE are kept together in [[logical schema|schemas]]. Schemas serve the same purpose as [[Java package]]s or [[namespaces]] in .NET, but have a hierarchy, and inherit classes from superschemas. This becomes useful especially when programming using the [[model–view–controller]] methodology, as model classes can be put in one schema, then the controller and view classes can be built on top of the model classes in a subschema.
 ===Program structure===

JADE (programming language): Difference between revisions

wikipedia>Comp.arch