Re: Keywords and Namesapces
- Posted by Vinoba Oct 03, 2011
- 40588 views
"As new libraries are written, we'd likely have additional collisions." If we can use some low level software such as Euphoria, to scan the functions and look for key word and similar conflicts, the developer writing "new libraries" can avoid 110% of the time.
Addressing the issue of long names and 1600 functions, it is a relatively easy matter to condense to about 600 functions or even less. Where we have in wxEuphora: long_name_function_to_do_something(atom wind, sequence xyz)
long_name_function_to_do_nextthing(atom wind, sequence xyz)
long_name_function_to_do_goodthing(atom wind, sequence xyz)
long_name_function_to_do_specialthing(atom wind, sequence xyz)
long_name_function_to_do_uniquething(atom wind, sequence xyz)
we can change it to
long_name_function_to_do_everything(atom wind, sequence xyz, integer thingnumber)
thingnumber: 1 = something, 2=nextthing, 3=goodthing, 4=specialthing, 5=uniquething
A simple Euphoria routine in the wxeud.e can take care of these 5 alternative branches of one function and connect to the appropriate 5 C routines.
