We have one vote for docs/dev.
Daniel Grunblatt.
On Wed, 17 Jul 2002, Melvin Smith wrote:
> At 06:14 PM 7/16/2002 -0700, John Porter wrote:
>
> >Melvin Smith wrote:
> > > I put it temporarily in the root dir, which I know is wrong.
> > > Where should .dev files go, anyway?
> >
> >Actually, I t
Melvin Smith wrote:
> Hmm, looking at the source directory, I'm starting to think
> maybe that isn't so good, it is pretty busy already.
>
> We have one vote for a /dev directory.
Actually, I think Dan did -- or at least was going to do --
something about this last night. Part of it was to sho
At 06:14 PM 7/16/2002 -0700, John Porter wrote:
>Melvin Smith wrote:
> > I put it temporarily in the root dir, which I know is wrong.
> > Where should .dev files go, anyway?
>
>Actually, I think that's right.
>..dev files live alongside their .c/.h siblings, no?
Hmm, looking at the source direct
Well, the .h files live elsewhere, but yeah, for now I think .dev files
should live with the .c files. Unless someone has an alternative
suggestion.
I'll update "make check_source" and pdd07 to reflect this.
--Josh
At 18:14 on 07/16/2002 PDT, John Porter <[EMAIL PROTECTED]> wrote:
>
> Me
Melvin Smith wrote:
> I put it temporarily in the root dir, which I know is wrong.
> Where should .dev files go, anyway?
Actually, I think that's right.
..dev files live alongside their .c/.h siblings, no?
--
JohnDouglasPorter
__
Do You Yahoo!?
At 05:08 PM 7/15/2002 -0700, Stephen Rawls wrote:
>Ok, I cleaned up the file a little bit, and added pod
>declarations. Should be finalized or close to it at
>least. If anyone likes it, I'll start working on
>making a .dev file for some other files, and start
>asking questions while I'm at it pr
Ok, I cleaned up the file a little bit, and added pod
declarations. Should be finalized or close to it at
least. If anyone likes it, I'll start working on
making a .dev file for some other files, and start
asking questions while I'm at it probably :)
Stephen Rawls
Stephen Rawls:
# I've only been involved with parrot since last week,
# but I've been learning quickly from all the
# documentation. With the recent activity about lack of
# documentation, I thought I'd try to help out as best I could.
# I've attached a file for an rx.dev candidate.
# Some
