> -Original Message-
> From: Mooney Christophe-CMOONEY1 [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, July 12, 2001 3:33 PM
> To: 'Rogirio Brito'; [EMAIL PROTECTED]
> Subject: RE: multiple entry/exit points
>
> Personally, i am very liberal wit
Hi Kurt,
Actually , it's quite common to have multiple entry and exit points.
Even in C++ if you write Object Code ... your constructors can
be overriden (different entry points ) and any method can exit
anywhere ... If you've only used C++ to code procedural style
this would lead you
Personally, i am very liberal with my lasts/breaks/returns/gotos.
There is definitely something to be said for strictness. From a theoretical
point of view, the code flows better. For example, it is easier to diagram
and easier to debug. If i write code for the company i work for, i follow
the
On Thu, 12 Jul 2001, Rogério Brito wrote:
On Jul 12 2001, Kurt Edmiston wrote:
> I guess I'm just curious to know what other more experienced Perl
> programmers think about this. I still adhere strictly to the "one way
> in, one way out" philosophy, mainly for the sake of readability. But
> I u
On Jul 12 2001, Kurt Edmiston wrote:
> I guess I'm just curious to know what other more experienced Perl
> programmers think about this. I still adhere strictly to the "one way in,
> one way out" philosophy, mainly for the sake of readability. But I
> understand how much easier it can make a
--- Kurt Edmiston <[EMAIL PROTECTED]> wrote:
> Here's a topic for discussion:
And a good one. =o)
> Coming from C++-land, I've always been taught over and over again
> that all subroutines/functions/blocks/etc should have only a single
> entry point and a single exit point. "It's just good pr
At 11:28 12.07.2001 -0400, Kurt Edmiston wrote:
>Here's a topic for discussion:
>
>Coming from C++-land, I've always been taught over and over again that all
>subroutines/functions/blocks/etc should have only a single entry point and
>a single exit point. "It's just good programming practice."
On Jul 12, Kurt Edmiston said:
>Coming from C++-land, I've always been taught over and over again that all
>subroutines/functions/blocks/etc should have only a single entry point and
>a single exit point. "It's just good programming practice." But now in
>the world of Perl, I've observed tha
Kurt Edmiston said:
> Coming from C++-land, I've always been taught over and over again
> that all subroutines/functions/blocks/etc should have only a single
> entry point and a single exit point.
Works great in theory ;) Especially if you have exceptions.
It's just not practicle/readable to alw
Here's a topic for discussion:
Coming from C++-land, I've always been taught over and over again that all
subroutines/functions/blocks/etc should have only a single entry point and
a single exit point. "It's just good programming practice." But now in
the world of Perl, I've observed that a
10 matches
Mail list logo
