JADE (programming language): Difference between revisions

No edit summary
No edit summary
Line 10: Line 10:


===Programming model===
===Programming model===
Lik e all of the other popular programming languages used to create database-driven software, JADE is [[Object-oriented programming|object-oriented]] to the core. JADE was designed to have all the most important features of object-oriented programming, but it was also designed to make programming simple, and so does not exhibit the full range of tools that some other languages do. For example, JADE does not support the overloading of methods or operators. This may seem like a big loss to some programmers, but for programming database applications which is what JADE is designed for, the parts that are left out do not end up being major drawbacks, as they are almost never needed. One notable feature that JADE lacks is parameterised constructors and this leads to some dangerous consequences in that one can never know if an object has been properly initialized.
Like all of the other popular programming languages used to create database-driven software, JADE is [[Object-oriented programming|object-oriented]] to the core. JADE was designed to have all the most important features of object-oriented programming, but it was also designed to make programming simple, and so does not exhibit the full range of tools that some other languages do. For example, JADE does not support the overloading of methods or operators. This may seem like a big loss to some programmers, but for programming database applications which is what JADE is designed for, the parts that are left out do not end up being major drawbacks, as they are almost never needed. One notable feature that JADE lacks is parameterised constructors and this leads to some dangerous consequences in that one can never know if an object has been properly initialized.


Classes in JADE are kept together in [[schema]]s. Schemas serve the same purpose as [[Java packages]] or [[namespace (computer science)|namespaces]] in .NET, but they are much different in the fact that schemas 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 [[schema]]s. Schemas serve the same purpose as [[Java packages]] or [[namespace (computer science)|namespaces]] in .NET, but they are much different in the fact that schemas 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.