[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

509.0. "T1.1.0 Event Specifications" by COOKIE::KITTELL (Richard - Architected Info Mgmt) Mon Dec 03 1990 19:24


I looked at the DNA .MS files on DSSR::NCLMSL: for the syntax of EVENT
specifications a while back, and have been putting them in my specs. But
the T1.1.0 MSL compiler won't parse them, even though the X1.1.0 compiler
didn't complain. I ordered the new SRM volumes as soon as the numbers were
posted, but in the meantime...

What is wrong with this?

       EVENT Cart Name Low = 48 :
          COUNTED AS Cart Name Lows,
       END EVENT Cart Name Low;
 
The attribute Cart Name Lows does exist in the Counters partition.
T.RTitleUserPersonal
Name
DateLines
509.1Try thisTENERE::LAVILLATTue Dec 04 1990 06:249
This is the correct syntax :

       EVENT Cart Name Low = 48 :
          COUNTED AS = (Cart Name Lows),
       END EVENT Cart Name Low;
 
Regards

Pierre.
509.2Thanks, worked like a champCOOKIE::KITTELLRichard - Architected Info MgmtTue Dec 04 1990 14:240
509.3Bug! Kill it before it spreads!CAPN::SYLORArchitect = Buzzword GeneratorWed Dec 05 1990 01:1610
    Is there any rational at all for why you changed the syntax from that
    in the NCL MSLs?
    
    This is yet another inconsistency that will have to be fixed in the
    next version of MCC. Surely it would be easier to prevent these
    bugs from spreading into thousands of lines of MSL that will
    simply have to be changed by hundreds of AM developers.
    
    Fix this bug now before it spreads!
    						Mark
509.4events with no text will not be displayable by FCL V1.1TOOK::DITMARSPeteThu Dec 06 1990 14:3111
The GETEVENT processing in FCL requires that a text definition be
present for any event defined in the dictionary.  This restriction will be
documented in the V1.1 release notes.

So, if you're going to be doing GETEVENTs (or NOTIFYs) on those events, give
it some text:

       EVENT Cart Name Low = 48 :
          TEXT = "Cart Name Low",
          COUNTED AS = (Cart Name Lows),
       END EVENT Cart Name Low;
509.5meet the rest of us halfwayNAC::ENGLANDThu Dec 06 1990 22:5112
    re .3: I second that emotion.  I coded to MCC SRM T1.0.0, the previous
    replies suggest that MCC's compiler will no longer compile MSLs from
    the NCL registry.  Is this an accurate problem statement? Was this
    NECESSARY? Gratuitous changes to MSL  cost the company money. There are
    at least 4 MSL compilers and 2.5 registries now. Lack of backwards
    compatibility was not justified here.  We should be working towards
    decreasing the # of compilers, not increasing them.  
    
    I heard a rumor that someone was fixing the MSL compiler to compile
    both NCL and MCC MSLs, so DECnet-VAX and the OSIrouter folks could
    use MCC's compiler.  This would be a big help in the short-term.
    
509.6Digital Does the Standards ThingTOOK::GUERTINI have an in_e, you have an out_eFri Dec 07 1990 12:006
    I don't want this to turn into a flame-throwing contest.  We all want
    to "do the right thing".  Certainly one multiplatform MSL translator
    always compiled from the same source code will go a long way to
    ensuring consistency and a "real" standard MS language.
    
    -Matt.
509.7Here there is a standard, implement itCAPN::SYLORArchitect = Buzzword GeneratorTue Dec 11 1990 12:4816
Re .4:

It appears that the original meaning of the "text" and "Name" properties
of an event/response/exception are in danger of being lost.

The name of the event is its name and what you shall display when displaying
an event report in any form. The event's name is followed by a list of 
arguments, each argument being an <argument name> = <value> display.

The text for a name is an expansion/convienience, it allows the above display 
to be **augmented** by additional narative text. It shall not be construed as
a replacement to the above display. Your PM might allow a user to 
chose whether the narative or the standard display is shown in a window or
on a screen, but you must allow the standard display to be shown.

					Mark