GNU bug report logs - #44186
Recursive mkdir

Previous Next

Full log

View this message in rfc822 format

From: divoplade <d <at> divoplade.fr>
To: Ricardo Wurmus <rekado <at> elephly.net>, Bengt Richter <bokr <at> bokr.com>
Cc: 44186 <at> debbugs.gnu.org, zimoun <zimon.toutoune <at> gmail.com>
Subject: bug#44186: Recursive mkdir
Date: Sun, 25 Oct 2020 10:07:17 +0100

[Message part 1 (text/plain, inline)]

Hello!

Le dimanche 25 octobre 2020 à 08:45 +0100, Ricardo Wurmus a écrit :
> > > To be clear, you would rather have that function as guile code
> > > rather
> > > than extending the C function? I'm OK with that, but in which
> > > file
> > > should I put that function? My instinct was to put the code near
> > > the
> > > mkdir function, and that happened to be in a C file, so I went C.
> 
> We should all be writing fewer lines of C code and more Scheme :)

OK, but where do I put the function? There is a posix.scm, but this
function is not posix, and posix.scm does not seem to export functions.

By default I will put it in ports.scm, because it is useful for open-
output-directory.

Also, I still cannot run the ports tests! How do I do it? Also test-
out-of-memory fails, but it also fails on master.

Attached, the new version for you to read!

Best regards,

divoplade

[0002-Use-the-recursive-mkdir-function-in-file-output-proc.patch (text/x-patch, attachment)]

[0001-ports-Add-mkdir-recursive.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.