Brent Clark wrote:
Hi all
Hi there
I seem to be having a few run ins with the "Project Leader", in terms of
my coding style.
Im very much for modularizing my work - hence the OO concept. That is
creating packages using return in my subroutine etc (Oh and using strict)
But the ex Cobol Projec
On 4/20/06, Brent Clark <[EMAIL PROTECTED]> wrote:
snip
> I really dont want to be a perl programmer that uses another languages
> technics etc.
snip
Yeah, its not like Perl uses techniques from AWK, Sed, Shell, C, Ada,
Lisp, Haskell, etc.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additio
Jenda Krynicky wrote:
They say you can write Fortran in any language I guess this guy tries to write
Cobol.
I think thats what im fighting against.
I really dont want to be a perl programmer that uses another languages technics
etc.
And also I dont want to use / write another persons style.
Typically, it's been my experience that the guy signing the paycheck, or the
one in charge of the project, is the guy calling the shots. If he wants to
utilize a coding technique that is neither secure nor understandable, then
he will eventually reap the benefits of his narrow-mindedness. If you h
> -Original Message-
> From: Brent Clark [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 20 April, 2006 09:39
> To: Perl FAq
> Subject: Coding Styles
>
>
> Hi all
>
>
> I seem to be having a few run ins with the "Project Leader", in
>
Brent Clark wrote:
Hi all
Howdy,
I seem to be having a few run ins with the "Project Leader", in terms of
my coding style.
Im very much for modularizing my work - hence the OO concept. That is
creating packages using return in my subroutine etc (Oh and using strict)
But the ex Cobol Proj
Hi all
I seem to be having a few run ins with the "Project Leader", in terms of my
coding style.
Im very much for modularizing my work - hence the OO concept. That is creating
packages using return in my subroutine etc (Oh and using strict)
But the ex Cobol Project Leader does not want .pm. V
