So many ways in XTalks

[Scott Morrow]

<snip>
> ...is that a return in a function (or a command but that's more  
> difficult to understand)  stops the running handler and returns  
> immediately a result disregarding next statements.
</snip>

A light bulb (if somewhat dim) just went on over my head... thanks.



<snip>
>  For most things, readability is better than being too concise,  
> especially when we're posting example code to this list.
</snip>

Still, as in the above example (for me) I appreciated being challenged  
to understand something outside of what I already knew and used.   
These multiple examples often give me insight into generalizations  
about how to use the language better.  I suspect that at the  
intermediate stages, many "readability" preferences are specific to  
the individual's understanding of the rev language.  I remember when I  
needed to write:
<  if the hilite of btn "foo" is "true" then  >
in order to make it easy to understand, whereas now
  <  if the hilite of btn "foo" then  >
  serves the same purpose with just as much readability.

Thank you all for the time and care it takes to write these examples.

<snip>
> ... copy someone's excellent code and just use it like a monkey...

</snip>

Yes!  Pass the bananas, please.   :  )
Scott Morrow

Elementary Software
(Now with 20% less chalk dust!)
web       http://elementarysoftware.com/
email     scott at elementarysoftware.com
------------------------------------------------------






On Jul 24, 2008, at 11:41 AM, Eric Chatonet wrote:

> Writing tutorials, I'm probably depraved :-)
> Or for other reasons...
>
> What I wanted to point out but it's possible I missed it ;-) is that  
> a return in a function (or a command but that's more difficult to  
> understand)  stops the running handler and returns immediately a  
> result disregarding next statements.
> I remember (when I was a bit younger ;-) that discovering this was  
> great. May be it's obvious for all now?
>
> And don't tell me I'm an old man ;-)
> Have a nice day.
>
> Le 24 juil. 08 à 20:23, J. Landman Gay a écrit :
>
>> Eric Chatonet wrote:
>>> Dear Jacque,
>>> You are right (as Ken was in a recent post).
>>> But my goal is always readability and elegance:
>>> e.g. no break, no 'and' and no 'or': something understandable at  
>>> first sight without racking one's brains...
>>> I always prefer it to concision even if I'm able to write put  
>>> CleanText(StripCR(toUpper(myList))) into tResult ;-)
>>
>> I know, and I agree, and I wasn't really too serious. :) For most  
>> things, readability is better than being too concise, especially  
>> when we're posting example code to this list.
>>
>> -- 
>> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
>> HyperActive Software           |     http://www.hyperactivesw.com
>
> Best regards from Paris,
> Eric Chatonet.
> ----------------------------------------------------------------
> Plugins and tutorials for Revolution: http://www.sosmartsoftware.com/
> Email: eric.chatonet at sosmartsoftware.com/
> ----------------------------------------------------------------
>
> William Humphrey wrote:
>> I like that especially when I can understand it. Very often I copy  
>> someone's
>> excellent code and just use it like a monkey...
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution