Re: Discriminated records are not the most efficient, but ...

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Mon, 23 Aug 2010 05:06:53 +0200, Peter C. Chapin <chapinp@acm.org> a  
écrit:
> Tasks aren't compilation units because they can't be compiled on their
> own. They must be contained in something else (such as a package or
> subprogram).
>
> Peter
I see the point, but... this is the same for functions and procedures  
(except the entry point procedure or function).

I've just checked deeper: compilation_unit includes subunit, which  
includes separates, which can be a separate task_body (follow links  
starting at 10.1.1). But, if you follow from compilation_unit to  
library_unit_declaration, you cannot reach anything like a task (or a  
protected).

Detailed:

    * subunit may be: separate (parent_unit_name) subprogram_body |  
package_body | task_body | protected_body
    * library_unit_declaration may be: subprogram_declaration |  
package_declaration | generic_declaration | generic_instantiation
    * library_unit_body may be: subprogram_body | package_body

So task or protected are compilation_unit... only when separate ? So what  
makes it not a compilation_unit when not separate ?

Unless I am missing something else, this seems strange to me.

-- 
* 3 lines of concise statements is readable, 10 pages of concise  
statements is unreadable ;
* 3 lines of verbose statements may looks unuseful, 10 pages of verbose  
statements will never looks too much pedantic