[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

81.0. "Remark on "Argument with no default"" by BYBLOS::TAMER () Wed Mar 21 1990 15:20

I am using the EFT Kit.  Problems that I encoutered with ILV-encoding of 
constructor data types are gone. Thanks folks.

I tested the argument to directives as documented in tables 7.1 and 7.2 in 
chapter 7 of the SRM.  All combinations of REQUIRED  versus DEFAULT work as
tables 7.1 and 7.2 say, except one: 

The second entry of table 7.1 says that when the user supplies an argument 
without a value and that argument does not have a default specified, 
the PM prompts for the argument value. The PM does not prompt for the value in
this case, it gives the following error message:

 
MCC> create subsystem sub fstest1
%MCC-W-VALUEMISSING, The attribute/argument value is missing

where

ARGUMENT Fstest1 = 4 : FileSpec
                ECHO = TRUE,
                DISPLAY = TRUE,
                REQUIRED = FALSE,
                SYMBOL = ARG_CREATE_FSTEST1
END ARGUMENT FSTEST1;


The same message is also given when REQUIRED=TRUE and DEFAULT=NO DEFAULT                          
T.RTitleUserPersonal
Name
DateLines
81.1INFO - expected resultsGOSTE::CALLANDERWed Mar 21 1990 17:4416
    To tell you the truth I had never read the table in the manor you did,
    but it is a reasonable request. We will have to view what we do then
    for version 1 as being restricted. 
    
    If a command has an attribute/argument that is required, and you don't
    enter the attribute/argument at all, then you are prompted for it; if
    you enter the attribute/argument name then you must have a default or
    enter the value. 
    
    Try something like this should happen....

    MCC> CREATE SUBSYSTEM SUB
    FSTEST1 = 
    
    
81.2BYBLOS::TAMERThu Mar 22 1990 09:0013
Re -1 

Although the action taken is inconsistent with the table entry, I agree it
is not a big deal. However, what about the following :

    MCC> CREATE SUBSYSTEM SUB Fstest1 = 
    MCC>

If "=" is included nothing happens. No error message and no dispatch to the 
routine. Just another TRM prompt.

When "=" was not entered after Fstest1, I got the error message mentioned in .0
Isn't there an inconsistency here ?
81.3INFO - I will qar thatGOSTE::CALLANDERThu Mar 22 1990 11:456
    
    what happened is that the space was encoded. This is really
    inconsistent. I will qar it, we should return an error.
    
    jill
    
81.4Thanks.BYBLOS::TAMERThu Mar 22 1990 15:560