| 1 |
On 29 September 2013 08:51, Ciaran McCreesh |
| 2 |
<ciaran.mccreesh@××××××××××.com>wrote: |
| 3 |
|
| 4 |
> The only reason anyone can make that claim is that no-one really knows |
| 5 |
> what slot dictionaries are or how they'd work in practice. Until |
| 6 |
> there's a rough description of how they work and a prototype |
| 7 |
> implementation, "subslot dictionaries" is like "magic beans". |
| 8 |
> |
| 9 |
|
| 10 |
Indeed, but I can basically say without looking at such a competing |
| 11 |
strategy, that as insane as the prototype may be in practise, it would be |
| 12 |
grossly preferable to have that mechanic as an internal dependency control |
| 13 |
mechanism, instead of something that more-or-less amounts to enumerating |
| 14 |
the contents of a large package ( perl ), and essentially converting all |
| 15 |
the file names in that package to a distinct USE_EXPAND useflag, and then |
| 16 |
basically making them *ALL* on by default and having to tell users "Don't |
| 17 |
turn them off unless you're smart/stupid!". |
| 18 |
|
| 19 |
That'd be like shooting somebody in the head as a cure for cancer. |
| 20 |
|
| 21 |
|
| 22 |
-- |
| 23 |
Kent |
Archives