|
From: <gr...@us...> - 2002-10-15 07:58:08
|
On Tue, 15 Oct 2002, Richard Jones wrote:
> On Tue, 15 Oct 2002 1:17 am, David Goodger wrote:
> > One thing to take out of this, is to compare how different tools
> > generate their collections of files. Epydoc makes one directory with
> > a slew of files, some with *very* long names, like
> > "docutils.parsers.rst.states.EnumeratedList.html". I'd much prefer to
> > use the filesystem to organize files hierarchically, as in
> > "docutils/parsers/rst/states/EnumeratedList.html". This was one of
> > the reasons I got interested in auto-documentation in the first place:
> > pythondoc did the long name thing, and MacOS classic couldn't handle
> > it with its 38-char filename limit.
what is the difference between
"docutils.parsers.rst.states.EnumeratedList.html"
"docutils/parsers/rst/states/EnumeratedList.html"
def create_file( class_name ):
fname = class_name . ".html"
if not flat:
fname.replace(".","/")
ensure_directory_exists( fname )
return open(fname,"w")
actually on the mac it should look like this.
"docutils:parsers:rst:states:EnumeratedList.html"
>
> Note that OSX still has that limit in places (tar, of all things, unless it's
> been fixed in a recent patch release).
>
>
> > So here's a requirement: when splitting files, each split level should
> > generate a new directory rather than another segment of a compound file
> > name.
>
> Seems reasonable enough to me, as long as there's a good TOC :)
--
BINGO: definitive merger agreement
--- Engelbert Gruber -------+
SSG Fintl,Gruber,Lassnig /
A6410 Telfs Untermarkt 9 /
Tel. ++43-5262-64727 ----+
|