Subject: RE: SDL-News: significance of <<...>> in sdl specification.
From: Erik Mats (Erik.Mats#telelogic.com)
Date: Mon Mar 24 2003 - 00:11:55 GMT
Become an SDL Forum Society member <http://www.sdl-forum.org/Society/members.htm>
The originator of this message is responsible for its content.
-----From Erik Mats <Erik.Mats#telelogic.com> to sdlnews -----
Hi Sachin,
this construct is a "path identifier", which specifies in which scope your
process is located.
To further explain this, let me modify your example for clarity by renaming
the process and the block:
block B;
...
process P referenced;
endblock B;
process <<block B>> P;
...
endprocess <<block B>> P;
The "path identifier" tells us that P is located inside B. Spontaneously, I
think in this particular example the path identifier is redundant, but it
could be required in situations where several referenced units share the
same name.
You might want to compare this with the "::" namespace operator in C++;
consider the difference between the following two method definitions:
void C::M() {}
void M() {}
This type of identifier can be very useful in your code, if you need to
override name shadowing to access variables in enclosing scopes, or if you
need to override a predefined data definition, such as in this example:
SYNTYPE Real = <<PACKAGE Predefined>> Real
...
ENDSYNTYPE;
(Note that in this case, if you omit the path identifier, the syntype
introduced will reference itself, rather than the one in the predefined
packaged.)
In some cases, this type of redefinition can be useful to tweak e.g. the
built-in datatypes (at http://www.telelogic.com/resources/ you can find an
example of using this in Tau SDL Suite simulation; search for "Customizing
SDL Simulations and Traces using Abstract Data Types").
For even more information, you may refer to section 2.2.2 of Z.100 (SDL-92)
or 6.3 of Z.100 (SDL-2000).
I hope this helps.
Best regards
/Erik
------------------------------------------------------------------------
Tau Generation2 - Development Visualized. Productivity Realized.
Learn more about Telelogic's new system and software development solution
at:
<http://www.taug2.com>
------------------------------------------------------------------------
Erik Mats
Senior Technical Support Engineer, Team Lead, Tau Support
Telelogic North America Inc,
400 Valley Road Ste 200, Mount Arlington NJ 07856
http://www.telelogic.com
mailto:erik.mats#telelogic.com
Phone: +1-973-770-5830
Fax: +1-973-770-6401
Telelogic - Automating the development lifecycle!
------------------------------------------------------------------------
-----Original Message-----
From: s p [mailto:spowar11#yahoo.com]
Sent: Friday, March 21, 2003 7:48 PM
To: sdl-forum
Subject: SDL-news: significance of <<...>> in sdl specification.
Become an SDL Forum Society member
<http://www.sdl-forum.org/Society/members.htm>
The originator of this message is responsible for its content.
-----From s p <spowar11#yahoo.com> to sdlnews -----
Hello,
In the textual specification of a system I have
statements of the kind:
---------------------------------
block ABC;
...
process ABC referenced;
endblock ABC;
process <<block ABC>> ABC;
...
endprocess <<block ABC>> ABC;
---------------------------------
What do "<<...>>" signify?
Thanking in advance.
-Sachin.
__________________________________________________
--End text from s p <spowar11#yahoo.com> to sdlnews ---
For extra SDL Forum Society benefits join at
<http://www.sdl-forum.org/Society/members.htm>
or (iff this does not answer your question) email:
owner-sdlnews#sdl-forum.org
--End text from Erik Mats <Erik.Mats#telelogic.com> to sdlnews ---
For extra SDL Forum Society benefits join at <http://www.sdl-forum.org/Society/members.htm>
This archive was generated by hypermail 2a23 : Thu May 09 2013 - 16:05:49 GMT