not there. any reason for that or is it just missing?
On Tue, Sep 23, 2008 at 04:15:10PM +0200, Arne Goedeke wrote: > not there. any reason for that or is it just missing? what is missing is links to functions of parent classes in the docs: http://pike.ida.liu.se/generated/manual/modref/ex/predef_3A_3A/Filesystem/Base/mkdir.html greetings, martin. -- -- cooperative communication with sTeam - caudium, pike, roxen and unix offering: programming, training and administration - anywhere in the world -- pike programmer working in china community.gotpike.org unix system- iaeste.(tuwien.ac|or).at open-steam.org administrator caudium.org is.schon.org Martin Bähr http://www.iaeste.or.at/~mbaehr/
Martin Bähr <mbaehr <at> email.archlab.tuwien.ac.at> wrote: > On Tue, Sep 23, 2008 at 04:15:10PM +0200, Arne Goedeke wrote: > > not there. any reason for that or is it just missing? > > what is missing is links to functions of parent classes in the docs: > http://pike.ida.liu.se/generated/manual/modref/ex/predef_3A_3A/Filesyste m/Base/mkdir.html Out of curiosity, why Filesystem.Base()->mkdir() and Stdio.mkdirhier()? -- -- Bertrand LUPART http://bertrand.gotpike.org/
You should probably wonder "why mkdir() and Filesystem...mkdir()". Filesystem solves other problems, for instance when you have a tar file or a remote filesystem. It was created as a base of making systems-that-contains-files with a common interface. mkdir() and Stdio.* exist because it's what you *usually* want to do without going circles before you get there. (mkdirhier() solves a superproblem of mkdir().)
RSS Feed