Re: S16: chown, chmod

2008-11-22 Thread Brandon S. Allbery KF8NH

On 2008 Nov 21, at 13:20, Larry Wall wrote:

On Fri, Nov 21, 2008 at 09:57:30AM -0800, dpuu wrote:
: On Nov 21, 9:16 am, [EMAIL PROTECTED] (Larry Wall) wrote:
: > Please feel free to whack on the spec
: The definition of C includes the statement that it's not
: available on most system unless you're superuser; and this can be
: checked using a POSIX incantation. I was wondering if it would be
: reasonable to provide this as a method on the chown function, so  
that


This won't work; _PC_CHOWN_RESTRICTED is per filesystem.   
(_POSIX_CHOWN_RESTRICTED is global but insufficient.)


--
brandon s. allbery [solaris,freebsd,perl,pugs,haskell] [EMAIL PROTECTED]
system administrator [openafs,heimdal,too many hats] [EMAIL PROTECTED]
electrical and computer engineering, carnegie mellon universityKF8NH




Re: S16: chown, chmod

2008-11-22 Thread Brandon S. Allbery KF8NH

On 2008 Nov 21, at 14:13, Dave Whipp wrote:
The restriction of chown to the superuser is a property of the OS,  
not the files. The example from the pod is:


man pathconf

--
brandon s. allbery [solaris,freebsd,perl,pugs,haskell] [EMAIL PROTECTED]
system administrator [openafs,heimdal,too many hats] [EMAIL PROTECTED]
electrical and computer engineering, carnegie mellon universityKF8NH




Re: S16: chown, chmod

2008-11-22 Thread dpuu
On Nov 22, 12:46 am, [EMAIL PROTECTED] (Brandon S. Allbery KF8NH)
wrote:
> On 2008 Nov 21, at 14:13, Dave Whipp wrote:
>
> > The restriction of chown to the superuser is a property of the OS,  
> > not the files. The example from the pod is:
>
> man pathconf

Ah, thanks for that.

It's probably an unproductive rats nest to attempt to add abstractions
for all these APIs, so I assume we'll have a "use IO::pathconf" pragma
that adds a global pathconf function, plus an IO.pathconf method, to
access these properties.



Embedding perl6 ?

2008-11-22 Thread Johan Holmberg
Hi!

I wonder if it is possible today to embed perl6 in a C/C++
application. What I would like to do is:

- distribute my application as a single executable
- have the perl runtime linked into the application
- be able to read+evaluate perl file(s) from my C++ code
- have the perl code call the C++ code I want to "expose" for perl

If this is possible, where should I look for examples/documentation?

/Johan Holmberg