Suggestion(s), add's to the brainstorming [Wink]

How about continnuing to let the the '.' be allowed in function names, and let the functions reference its returnvalue as the part after the '.' ?

Function name: Time.GetHours
Internal reference: $GetHours

Jens's example could then look like this:
code:
$hours=Time.GetHours(@TIME)
 
function Time.GetHours($time)
  Dim $splittime
  $splittime = split($time,':')
  $GetHours = $splittime[0]
endfunction
If this was allowed and all scripts was following this syntax when dealing with a 'class' it might be easier to read other peoples scripts.

But this is just cosmetic, you migth as well make your own function name convention, like: All function names starting with $tm has to do with time, the script would then be:
code:
$hours=tmGetHours(@TIME)
 
function tmGetHours($time)
  Dim $splittime
  $splittime = split($time,':')
  $tmGetHours = $splittime[0]
endfunction
This would work with the current version of KiX

- A second suggestion could be to let the function reference itself as me (new reserved word), the function could then be coded as:
code:
$hours=tmGetHours(@TIME)
 
function tmGetHours($time)
  Dim $splittime
  $splittime = split($time,':')
  me = $splittime[0]
endfunction
function name would then be irrelevant, ofcourse KiX should still support $FunctionName as internal reference.

-Erik

ps.
I like the idea of allowing functions inside functions, sort of a function only 'alive' when the parrent is active.
What about functions inside functions inside functions .................. [Eek!]