Mathematica: Webel ADT: The term 'Abstract Data Types (ADT)' is used informally (the Webel ADTs do not always adhere to strict definitions of ADTs). Please just think of it here as meaning a strong type or stateless "pseudo class".

Webel IT Australia promotes the amazing Mathematica tool and the powerful Wolfram Language and offers professional Mathematica services for computational computing and data analysis. Our Mathematica tips, issue tracking, and wishlist is offered here most constructively to help improve the tool and language and support the Mathematica user community.

DISCLAIMER: Wolfram Research does not officially endorse analysis by Webel IT Australia.

Icon class

icon_class

far fa-sticky-note

icon_class_computed

far fa-sticky-note

Note kind

EXPLANATION

Policy level

INFORMATIVE

Webel Mathematica keywords

ADT`

Webel ADT

Keywords

The use of the term Abstract Data Types (ADT) for OO-related constructs is a familiar term amongst Wolfram Language coders and the Mathematica community. It was in part popularised by Mathematica expert Roman Maeder, whose ADT recipe for the Wolfram Language has been (heavily) adapted - some may say mis-appropriated - by Webel IT Australia for use as a strong type or pseudo class.

Wikipedia offers a good general discussion of the formal concept Abstract Data Type concept; the use in the Webel recipe for ADTs with inheritance in Mathematica is less formal.

As used in the trails on this site prefixed as Webel ADT it does not mean a formal Abstract Data Type! It just means a stateless pseudo class.

Note also:

Mathematica: Webel ADT pseudo classes: POLICY: The Abstract Data Types (ADTs) are stateless functional (although inheritance and overrides are supported), with no caching by default (although there is nice optional caching using CreateUUID[] and Once[]).

Mathematica: Webel ADT pseudo classes: The ADT⊙get method may be used to access the '$$' wrapped primary. This is intended for development and testing purposes only (not for regular use by clients) since it BREAKS ENCAPSULATION!

There is further discussion at this slide page:

Webel ADTs include inheritance (and aren’t actually formal ADTs)

And there is a detailed slide trail section showing exactly how Webel ADTs are used and combined with SysMLv1 modelling here:

SECTION: The Webel Abstract Data Type (ADT) stateless pseudo-classes with inheritance (with SysMLv1 models)

Some departures from formal Abstract Data Type (ADT) usage are indicated by custom stereotypes with icons in the Webel SysML4Mathematica (v1) modelling:

Visit also: Mathematica: Webel ADT pseudo classes: The SysMLv1 models are supported by custom stereotypes with icons. Some of these indicate OO-similar use of ADT-Methods and departures from formal Abstract Data Type (ADT) definitions.

Relates to

Mathematica: POLICY NOTES for the Webel Abstract Data Type (ADT) pseudo classes with inheritance for the Wolfram Language

Dr Darren of Webel IT Australia makes the case for better object-orientation for Mathematica using pseudo class ADTs without losing the super-functional power of the Wolfram Language

Webel ADTs include inheritance (and aren’t actually formal ADTs)

Webel ADT hierarchy views as tree, graph, and SysML

Webel ADT`package: Some ADT pseudo class utility functions in a ::usage help viewer. Diagnostic, help, and development functions.

Mini SysMLv1 BDD view of the Webel ADT Block

SysMLv1 Internal Block Diagram (IBD) of the Webel ADT base class

Simple Webel ADT in the development view dV[adt] and class/methods help hC[adt]

Extending ADT sub-classes represented as SysML Blocks with redefined wrapped ‘$$’

Webel ADT SysMLv1 Stereotypes