My vote - drop support for periods in function names (fix the inconsistency) ... but allow support for "functions-within-functions" ... imho - this would go a long way in furthering the OO cause.

Maybe with a structure like this (just green-lighting here):

code:
 
class Adder(constructor $parms...)

  
 dim $n1,$n2
 
 
 function SetN1($n)
 
  $n1 = $n
 
 endfunction
 
 
 function SetN2($n)
 
  $n2 = $n
 
 endfunction
 

 function Add()
  
  $Add = $n1 + $n2
 
 endfunction
  
endclass
then you could instantiate and use the object, just like a COM object. The periods in function names would now refer to a function within the class.

code:
$Adder = Adder()
  
$Adder.SetN1(2)
$Adder.SetN2(2)
 
$Answer = $Adder.Add()
one can always create functions to set and get (mimmic) properties (SetN1/GetN1) ... thats how things normally work under the covers anyways (in COM) ...

[ 06. September 2002, 16:48: Message edited by: Shawn ]