[Pharo-project] OComplection

Stéphane Ducasse stephane.ducasse at inria.fr
Mon Aug 6 12:25:40 CEST 2012

> the more time I spend with OCompletion the more I think it's the wrong model:
> NECompletion provides in many cases way better / quicker results
> NOCompletion does tons of magic to increase the chances of a correct hit,
> neglecting
> - self sends
> - super sends
> - ClassSends
> which is basically the main source for getting nice input...
> I think NOCompletion should be removed. The only thing that might maintain
> is a Database which will give back a date for a given selector so we can
> sort them accordingly. But IMO that can be solved muuuuch easier.
> Things against NOCompletion:
> - not documentation whatsoever (no class comments no comments no categories... nada)
> - totally breaks type completion (self sends usw...)
> - duplication of NECompletion...
> Since I don't see anybody maintaining this dead body we should remove it
> from the system!

Why not but do we get the most recently typed because this is cool to have


More information about the Pharo-project mailing list