Newsgroups: perl.perl6.internals
From: j...@hitchhiker.org (Josh Wilmes)
Date: Wed, 10 Mar 2004 12:53:16 -0500
Local: Wed, Mar 10 2004 12:53 pm
Subject: Re: [PROPOSAL] C<stat> opcode and interface
I have no opinion either way on this opcode or the date/time ones, but I
would like to remind folks about miniparrot- if we want it to work again, there needs to be a smooth way to exclude opcodes or PMCs which are not expecially portable on its platform (pure c89, no threads, etc). This means one or more of the following will need to be done: Personally i'm leaning towards the third option, but I think we should be It's also quite possible that miniparrot is a waste of time. I'm pretty --Josh --Josh At 11:39 on 03/10/2004 +0100, Leopold Toetsch <l...@toetsch.at> wrote: > Proposal C<stat> opcode and interface
> 1) ops > stat (out PMC, in STR, in INT) > Return a new array-like[1] PMC $1 with file stats from file (PIO or > .PARROT_STAT_NO_FOLLOW_LINK > The array(-like) has keyed access with these keys > .PARROT_STAT_FILE_SIZE > .PARROT_STAT_MODE a bitmask with these bits: > .PARROT_STAT_PERM a bitmask with these bits > .PARROT_STAT_MTIME modified time > .PARROT_STAT_OS_TYPE a constant defining the os-specific > .PARROT_STAT_OS_SPECIFIC > 2) Interface > PMC* Parrot_stat_s(Interp*, STRING* file, INTVAL flags); > 3) Interface to platforms > INTVAL Parrot_stat_os_s(Interp*, Parrot_stat*, STRING* file, INTVAL > typedef struct _parrot_stat { > 4) Notes > [1] it needs just these vtables implemeted: I0 = P0[i], N0 = P0[i], > Comments, improvements, and implementations thereafter welcome You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| ||||||||||||||