Peter Funk said: > The library documentation provides a existing logical subdivision into > chapters, which group the library into several kinds of services. > IMO this subdivision could be discussed and possibly revised. > But at the moment I got the impression, that it was simply ignored. > Why? What's so bad with it? Ka-Ping Yee writes: > I did look at the documentation for some guidance in arranging > the modules, though admittedly it didn't direct me much. Fred L. Drake, Jr. writes: > The library reference is pretty well disorganized at this point. I > want to improve that for the 1.6 docs. Let me just mention where my inspirations came from: shame of shames, it came from Perl. It's hard to use Perl's organization as is, because it doesn't (view itself) as a general purpose langauge: so things like CGI.pm are toplevel, and regex's are part of the syntax. However, there are a lot of good hints there. -- Moshe Zadka <mzadka@geocities.com>. http://www.oreilly.com/news/prescod_0300.html http://www.linux.org.il -- we put the penguin in .com
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4