Webel: Programmers who can count higher than one (1) know that you don't have to choose exclusively between object-orientation (and classes) and functional programming. You can have your cake and eat it. It's not XOR!

Icon class

icon_class

far fa-sticky-note

icon_class_computed

far fa-sticky-note

Note kind

Keywords

And besides, "object-oriented" Classes can be used primarily as an organisational strategy in combination with functional programming strategies without any use of state (if that's what you want). To use Classes is NOT to adopt every aspect of all object-oriented programming paradigms!

Or, you can use the Abstract Data Type (ADT) approach in Mathematica, which combines splendidly with the "super functional" capabilities of the Wolfram Language:

TIP: Mathematica: Webel's ultimate guide to using Abstract Data Types to create "pseudo classes" (strong types) with inheritance for the Wolfram Language, all modelled in SysML!

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

Relates to

The Webel Recipe for SysML-friendly Wolfram Language coding in Mathematica

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

A word on classes and object orientation for Mathematica

Representing the SysMLv1 Block and SysMLv2 Part Def in Mathematica requires classes and object orientation (OO)

SysMLv1 vs SysMLv2

Related notes