A type of Prefix which allows the developer to separate blocks of code into organized, defined parts to help provide clarity of the logical block and add structure to the code.
Takes one parameter, Name
Takes two parameters, TableName, IfLenFld
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Takes one parameter, Status
Takes three parameters, Location, ClassNames, AlertText
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes no parameters.
Takes two parameters, Data, Boundary
Has no parameters
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes no parameters
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes two parameters, TableName, IfLenFld
Takes one parameter, FieldName
Takes one parameter, ProcedureName
Takes one parameter.
The MOX coding and programming language pays heritage to BASIC, but has been crafted for the specific type of work and environment that is demanded of Moxie.Build.
This style guide provides comprehensive standards for writing clean, maintainable, and consistent MOX code for Moxie.Build. Code examples on this page are for illustrative purposes and are only intended to demonstrate style conventions.
Takes one parameter, SlowWritePercent
Has no parameters
Takes two parameters Command, Options
Takes two parameters, Source, Search
Takes one parameter.
Has no parameters