On Thu, Nov 21, 2013 at 11:43 AM, Martin Schreiber <[email protected]> wrote:
> On Thursday 21 November 2013 13:48:37 Marcos Douglas wrote:
>
>> >> WOW! Exotic too much and worse then use "result" variable.
>> >
>> > Why? It shows clearly that it is a write only variable which can not be
>> > read and can't be forgotten to set.
>>
>> "end" is a reserved word, not a variable so it can't receive a value!
>> Better to use "return" or continue using "result", IMO.
>>
> 'end' here is the end of the procedure block with starts with a result type
> definition:
> "
> sub func1(): int32;
> begin
> end:= 123;
> "

I did understand and I continue disagreeing.

> which means assign the sub block with a value. Not that bad when the shock is
> over. ;-)

I don't think so.  :/

--
Marcos Douglas

------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
mseide-msegui-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Reply via email to