--- John <[EMAIL PROTECTED]> wrote:
> Does anyone have a cheetsheat for function prototyping - how to say
> that a parameter is a scalar, array, hash, reference, etc., and whether
> it is required or optional?
John,
Here's the cheatsheet for function prototypes:
Don&#
On Tue, 2002-01-29 at 15:38, John wrote:
> Does anyone have a cheetsheat for function prototyping - how to say
> that a parameter is a scalar, array, hash, reference, etc., and whether
> it is required or optional?
>
>
>
>
>
>
>
> --
> To unsubscr
Does anyone have a cheetsheat for function prototyping - how to say
that a parameter is a scalar, array, hash, reference, etc., and whether
it is required or optional?
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--- Aaron Craig <[EMAIL PROTECTED]> wrote:
> At 15:12 22.05.2001 -0700, you wrote:
> > > > The problem is: PROTOTYPES MUST BE SEEN BEFORE THE FUNCTION IS
> > > > CALLED. So few people realize that (for one reason or
> > > > another[1]).
>
> > For that reason, I usually do my function definitions
At 15:12 22.05.2001 -0700, you wrote:
> > > The problem is: PROTOTYPES MUST BE SEEN BEFORE THE FUNCTION IS
> > > CALLED. So few people realize that (for one reason or another[1]).
>
>For that reason, I usually do my function definitions at the top of my
>programs. That way they've already been t
> - Original Message -
> From: "Jeff Pinyan" <[EMAIL PROTECTED]>
> To: "Aaron Craig" <[EMAIL PROTECTED]>
> > Before I answer your question, I have to ask you to not use
> > subroutine prototypes. 9 out of 10 Perl programmers use them
> > incorrectly or don't know what they do.
> >
> > The
