[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

38.0. "PROBLEM : MSL LSE template error ?" by TENERE::DUNON (Paul Dunon - Telecom Engineering - VBO) Mon Jan 15 1990 15:31

Hi,

When I expand an attribute or an argument definition in LSE, the expanded line
CATEGORIES ends with a comma. This comma is then rejected by the MSL Translator.

Example:

   ATTRIBUTE xyz = 1 : SimpleName
   (* {text} *)
      ACCESS = SETTABLE,
      DISPLAY = TRUE,
      UNITS = "{text}",
      DEFAULT = "My name",
      SYMBOL = XYZ,
      CATEGORIES = ( CONFIGURATION ),  	<=========
   END ATTRIBUTE xyz;


Additionnaly, the messages generated by the MSL are not very helpful because
the parsing of the whole attribute definition is rejected.


Is it a known problem ?

					-- Paul
T.RTitleUserPersonal
Name
DateLines
38.1MSL template restriction in ReferenceTOOK::D_BLACKDarryl BlackTue Jan 16 1990 16:0516

    Is it a known problem?

    This is an MSL template restriction, not a problem.  Since many of the
    arguments for an attribute specification (as well as other stuff in an
    MS) are optional, the MSL template has no way of knowing which ones
    were chosen, which ones were deleted--hense each argument terminates
    with a comma--the more common case.  The translator expects the last
    item to not have a comma, in most cases.

    This restriction is discussed in detail in the documentation, top
    paragraph page A-3 (Toolkit Reference).
                                   
    Darryl

38.2suggestion qarGOSTE::CALLANDERWed Jan 24 1990 15:184
    
    A priority 5, suggestion, qar has also been entered against the
    MSL translator requesting a better message on an extra comma.