Initializing help system before first use

Upgrading from Mosel 2 to Mosel 3

Topics covered in this section:


This section describes the differences in language syntax, behaviour and the API between Mosel 3 and Mosel 2.X versions.

Language

  • 'count', 'counter' and 'with' are now keywords so these words and their all-uppercase form can no longer be used to name symbols.
  • By default 'initialisations' blocks now finalize the sets they initialize and also the index sets of initialized non-dynamic arrays (i.e., arrays not explicitly declared 'dynamic'). This may cause problems if the model modifies sets initialized via such a block or expects arrays of this kind always to be created dynamic. This automatic finalization functionality may be disabled by adding the following option to the model: 
    options noautofinal

Libraries

  • Deprecated routines 'XPRMgetdsoinfo' and 'XPRMgettypename' have been removed: 'XPRMgetdsoprop' and 'XPRMgettypeprop' must be used instead.
  • Functions 'XPRMgetvarnum' and 'XPRMgetctrnum' now require a model reference.

Native Interface

Mosel 3.0 accepts modules compiled for Mosel 2.4 but it no longer accepts modules compiled for Mosel 1.6. Upgrading requires the following changes:

  • Deprecated routines 'getdsoinfo' and 'gettypename' have been removed: 'getdsoprop' and 'gettypeprop' must be used instead.
  • Functions 'getvarnum' and 'getctrnum' now require a context.
  • The type function 'fromstring' now expects an extra argument to return a pointer to the first character not used by the conversion.
  • The function 'dsotypfromstr' now takes an extra argument to return a pointer to the first character not used by the conversion.

Parent Topic Upgrading to Mosel 6

© 2001-2025 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.