Re: Seeking for papers about tagged types vs access to subprograms

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

Le Tue, 14 May 2013 21:35:55 +0200, Robert A Duff  
<bobduff@shell01.theworld.com> a écrit:

> Yes.  I think what's missing is an ability to initialize an object
> after creating it (either by declaring it, or via "new").  My hobby
> language has that.  And it distinguishes syntactically between
> initialization and assignment_statement.
> […]
> I think allowing to separate initialization from declaration
> can solve that.

Does your hobby language has static or runtime check to catch access to  
uninitialized variables?

I don't see the point with deferred initialization, it seems to be an  
object state finally (states, again). Either you can tell a variable was  
or was not initialized, and then it has a state and it is finally  
initialized before you suppose it is, or else it can't tell the variable  
was not initialized because it really initialize nothing at the  
declaration, and then it's perhaps unsafe.

-- 
“Syntactic sugar causes cancer of the semi-colons.” [1]
“Structured Programming supports the law of the excluded muddle.” [1]
[1]: Epigrams on Programming — Alan J. — P. Yale University