Implicit defenitions

I can't say for sure, but one possibility is leaving the return type off a function declaration in which case it is assumed to be an integer. Another is implying template function parameters from the function arguements. If you have template < typename T > T f(T value) then you can call that as either f(a) or f < type > (a). In the first T is implied by the type of a. The second is explicitly stating T. Since you normally call it as f(a) and only explicitly state the type when you want to use some type other than a's type it seems a strange thing to issue a warning on. The only other thing I can think of is arguement dependant lookup (ADL). If you call f(N::T) then it will look in N for f. You can look at that as the scope of f is implied by the scope of its parameters. Well, not really the scope of f, but rather the scope of the expression calling f.

Frigging templates and their angle brackets.

[edited by - LilBudyWizer on January 25, 2003 12:50:08 PM]