8.2.2 Special considerations for C++

• All of the items in the previous section (see C) still apply.
• The ‘@{’ command is very useful for beautifying very short definitions of member functions such as constructors. See ATlb
• Essentially, FWEAVE has only one name space, global to the entire code; those names do not obey any concept of scope. In various situations in C and C++, however, multiple namespaces are used, or the interpretation of a name changes according to its scope. Thus, the design of FWEAVE imposes a few restrictions on one’s programming style. (Remember, FWEAVE doesn’t know nearly as much as a language compiler.)

  One example in C++ has to do with formal types in templates. Consider the following example:

  template <class Type>
  class A
  {
  private:
          Type *p;
  }
  

  In order that the class definition be typeset correctly, ‘Type’ must be understood to be a reserved word like int, and that is correctly figured out by the first class command. However, according to C++, the scope of ‘Type’ is local to the class definition; unfortunately, FWEAVE does not respect that locality and will always treat ‘Type’ as an int from the point of the ‘class Type’ construction to the end of the source code. Thus, one should use such dummy variables as ‘Type’ only as formal template parameters, never as ordinary variables.