From: Steve L. <st...@di...> - 2006-11-03 09:34:00
|
On 03/11/2006, at 1:28 PM, Joe English wrote: > Now if the platform package were the kind of thing we could > get right the first time, then sure, put it in the core and > _eventually_ everyone could rely on it (some sooner, some later). And this attitude is why Tcl is (in the eyes of many) a dead or dying language. At least the Debianistas understand that "stable" means "obsolete" :/ > But it's not: by its very nature, [platform::identifier] is > going to be perpetually incomplete and frequently out of date. > No matter how extensive the implementation, it's going to > be obsolete the moment somebody ports Tcl to a new platform. > > Of course putting it in tcllib won't make it universally > available either, but it *will* make it easier for people > who need the latest version to get it when they need it. Like I said, I'm more than happy for it to go into Tcllib, as well as be in Tcl itself. Now that I think about it, why is tcltest in Tcl and not Tcllib? ;-) >> Remember that the TIP authors are at the pointy-end of delivery >> multi- >> platform distributions and extensions - and only too aware of the >> problems that entails. > > Y'know, I've done a bit of development and deployment myself. Indeed - and you know I know that. Now, before I waste any more time p*ssing into the wind - what's the feeling of the TCT re #291. If Joe's attitude is the predominant one then I won't bother pushing this. Conversely, if the concept of #291 is reasonable and just needs refinement then I'm more than happy to invest the time. Just don't make me waste a bunch of time so you can say "hmmmm ... maybe not". Steve |