[erlang-questions] Function Dependency

Richard O'Keefe <>
Thu Aug 23 01:31:18 CEST 2012


A signature is basically a type for a module or a(n ML-style) functor.
The 'class signatures' that G++ has (or had) are that sort of thing.

In Python 3.3
http://www.python.org/dev/peps/pep-0362/
a signature is an object describing everything that is known
about the interface of a function:  two functions may well
have equal signatures.

C++ is seriously weird here (as ever):
  1.3.10 signature [defns.signature]
  the information about a function that participates in overload
  resolution (13.3): the types of its parameters and, if the
  function is a class member, the cv- qualifiers (if any) on the
  function itself and the class in which the member function is
  declared.  2) The signature of a function template specialization
  includes the types of its template arguments (14.5.5.1). ...
  2) Function signatures do not include return type,
  because that does not participate in overload resolution.

Like Python, it does *NOT* include the name of the function.
Unlike practically everyone, it also doesn't include the
result type.




More information about the erlang-questions mailing list