Hi,
    I have the following query w.r.t the usage of IMPORTS. Consider the following specification - 

Imports DEFINITIONS ::=
BEGIN
IMPORTS a FROM Exporting-Module;

a REAL ::= PLUS-INFINITY

--b INTEGER ::= a
--b REAL    ::= a

END

Exporting-Module DEFINITIONS ::=
BEGIN

a INTEGER ::= 1

END


Clause 12.19 of ITU-T: Where the "Symbol" also appears in an "AssignmentList" (deprecated), or appears in one or more other
instances of "SymbolsFromModule", it shall only be used in an "External<X>Reference". Where it does not so appear, it
shall be used directly as a "Reference".

    As per the above clause, I understand that neither declaration of b (commented) are permitted (a should have been used only through the use of External<X>Reference. But I have seen some ASN.1 tools accept the second definition of b (if un-committed). I wanted to clarify, that since the clause mentions the word "deprecated", is it that it is permitted though the compiler can choose a behavior of its own.

Yours Sincerely.
Ramaswamy

"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." - Albert Einstein

Information contained and transmitted by this E-MAIL is proprietary to
Synergy Infotech Private Limited and is intended for use only by the
individual or entity to which it is addressed, and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law. If this is a forwarded message, the content of this E-MAIL may not have
been sent with the authority of the Company. If you are not the intended
recipient, an agent of the intended recipient or a  person responsible for
delivering the information to the named recipient,  you are notified that any
use, distribution, transmission, printing, copying or dissemination of this
information in any way or in any manner is strictly prohibited. We have taken
precautions to minimize the risk of transmitting software viruses, but we
advise you to carry out your own virus checks on any attachment to this
message. We cannot accept liability for any loss or damage caused by software
viruses. If you have received this communication in error, please delete this
mail & notify us immediately at mailto:[EMAIL PROTECTED]

Reply via email to