This probably should be in the Features forum and will probably have to wait for POL 0.99 but here it is anyway.
How many times have you written the ultimate script and found that it just didn't perform as you had intended or didn't compile at all?
I propose a new internal function call,
DWIM.
This is an acronym for DoWhatIMean. It would use advanced AI and heuristic algorithms to determine what the scripter is attempting to do. Using scripts written by the scripter and the vast amount of public domain scripts that would be stored in the core internal database the DWIM instruction would, using state of the art interpolation and exstrapolation algorithms and extensive logic trees, analyse and perform the task that the scripter intended rather than what his/her script was written to do. At first it might not be able to adequately interpret the scripters desires but it would learn over time as more scripts were written. Perhaps a training mode could be implemented much like voice recognition software is trained to turn the spoken word into text.
I feel implementing this feature would end a lot of the problems we now see in buggy horribly written scripts and would streamline coding in general. Most would admit there is a need for such a function and I for one would put it to good use.
This could be made more useful as a compiler directive or even an eCompile option. An entry in the eCompile.cfg file such as the following could be offered.
Code:
DoWhastIMean 1 // 0 allows your scripts to be compiled as written, 1 invokes the DWIM override. Default is 1.
If it is added to eCompile then ofcourse the heuristics would be incorporated in the eCompile exe. Now that I think about it that's probably better because it keeps the core executable small and compact.
Anyway, that's my proposal.
I welcome your comments.
Doesn't the Microsoft Office paperclip have this feature too?