RE: About goto (was: fixed windows)
> From: Peter Willems <peter at integratedmoves.com>
> Subject: RE: fixed windows
>
>
> Christian.CUVIER at agriculture.gouv.fr wrote:
>
>
>> Actually, apart from integration in Office apps, I don't see many
>> reasons to use VB rather than Eu (oh yes, the debugger). Yet the user
>> base for Eu is tiny compared to VB's. Guess why?
>
>
> Ermm........ marketing budget 
>
>> Adding to my earlier statements about goto: what is sorely needed is
>> more flexible flow control, what I'd call structured or controlled goto.
>>
>> For instance: exit one or more if blocks, exit one or more loops at a
>> time, possibly labelling them - this is a real bonus in maintenance-.
>
>
> In WinDev there is a simple solution for this: return
> When you have a procedure with deeply nested loops and
> constructs, doing a return anywhere in that construct will
> break you out of the construct and back to the point after
> where the procedure was called.
>
Right. But putting the deep nesting tree in a separate routine is a
pain in Eu because of identifier scope issues. Nested routines would
admittedly solve that.
>
>> Matt recently remarked that the Eu user base seems mostly interested by
>> GUI building and hardly anything else. Since this is not your main use
>> for EU (/me not mine either), you don't get listened too much on this
>> list.
>
>
> I think that GUI building is important also, as we are living
> in a world where desktop machines are running windowed user
> environments. It is also the area where the supporting libraries
> and such are still lacking. Mind you I don't say I want it
> implemented inside Euphoria. As Eu is cross platform that would
> bring a lot of dead overhead to the interpreter, and greatly
> diminish the possible use because of differences between operating
> systems.
>
> Hans Peter Willems
CChris
|
Not Categorized, Please Help
|
|
