System.Posix.Process.executeFile question

[Frederik Eaton]

OK, I thought so. Is this the wrong mailing list for bugs in the
documentation though?

There is the markup problem, and it also says "executeFile cmd args
env" rather than "executeFile cmd usePath args env".

Frederik

On Tue, Aug 08, 2006 at 03:56:59PM -0700, Clifford Beshers wrote:
> That's the bit about 'whether or not the current PATH is to be searched'.  True means use the search 
> path.
> 
> Frederik Eaton wrote:
> >Hi,
> >
> >I'm wondering what the second argument to 'executeFile' is. It's not
> >clear from the documentation.
> >
> >http://www.haskell.org/ghc/docs/latest/html/libraries/unix/System-Posix-Process.html#v%3AexecuteFile
> >
> >Also, it seems the documentation source is being parsed incorrectly. This is what it looks like to 
> >me:
> >
> >executeFile :: FilePath -> Bool -> [String] -> Maybe [(String, String)] -> IO ()
> >literal>executeFile cmd args env</literal calls one of the function>execv*</function family, 
> >depending on whether or not the current PATH is to be searched for the command, and whether or not 
> >an environment is provided to supersede the process's current environment. The basename (leading 
> >directory names suppressed) of the command is passed to function>execv*</function> as 
> ><varname>arg[0]</varname; the argument list passed to function>executeFile</function therefore 
> >begins with varname>arg[1]</varname
> >
> >Thanks!
> >
> >Frederik
> >
> >  
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://www.haskell.org/mailman/listinfo/libraries
> 

-- 
http://ofb.net/~frederik/