From d0d265c0ac62c96ffcbfb75b105ca7c1e2b67b17 Mon Sep 17 00:00:00 2001 From: languagelawyer Date: Mon, 17 Aug 2020 10:53:39 +0300 Subject: [PATCH] [expr.call] [dcl.fct] Move return type requiremens --- source/declarations.tex | 5 +---- source/expressions.tex | 1 - 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/source/declarations.tex b/source/declarations.tex index 22e0824e7d..8651b1b066 100644 --- a/source/declarations.tex +++ b/source/declarations.tex @@ -3490,10 +3490,7 @@ \pnum \indextext{function return type|see{return type}}% \indextext{return type}% -Functions shall not have a return type of type array or function, -although they may have a return type of type pointer or reference to such things. -There shall be no arrays of functions, although there can be arrays of pointers -to functions. +The return type shall be a non-array object type, a reference type, or \cv{}~\tcode{void}. \pnum A volatile-qualified return type is deprecated; diff --git a/source/expressions.tex b/source/expressions.tex index 32a0f989fc..c7b04c259a 100644 --- a/source/expressions.tex +++ b/source/expressions.tex @@ -2949,7 +2949,6 @@ statically chosen function (i.e., ignoring the \tcode{virtual} keyword), even if the type of the function actually called is different. \indextext{type!incomplete}% -This return type shall be an object type, a reference type or \cv{}~\tcode{void}. If the \grammarterm{postfix-expression} names a pseudo-destructor (in which case the \grammarterm{postfix-expression} is a possibly-parenthesized class member access),