Re: type-checking [Was: What is Perl?]

2000-08-02 Thread Piers Cawley
Damian Conway [EMAIL PROTECTED] writes: Peter Scott [EMAIL PROTECTED] (I think -- Piers) writes: Though a good post condition would benefit from some sort of unconditional catch of return, I suppose. Perhaps allowing continue on the outer sub block... Argh, no! A good

Re: type-checking [Was: What is Perl?]

2000-08-02 Thread Simon Cozens
On Wed, Aug 02, 2000 at 02:18:07PM +1000, Damian Conway wrote: Though a good post condition would benefit from some sort of unconditional catch of return, I suppose. Perhaps allowing continue on the outer sub block... Argh, no! A good postcondition is either invisible to the

Re: type-checking [Was: What is Perl?]

2000-08-02 Thread Chaim Frenkel
"DS" == Dan Sugalski [EMAIL PROTECTED] writes: DS I think I'm missing the point. Why pull 'em out like that? Why not just put DS the code in the body of the sub? Though a good post condition would benefit DS from some sort of unconditional catch of return, I suppose. Perhaps DS allowing

Re: type-checking [Was: What is Perl?]

2000-08-02 Thread skud
On Tue, Aug 01, 2000 at 01:09:46PM -0800, Michael Fowler wrote: Several people have suggested strong typing as a feature, and have been shot down one by one. However, I think it can be done without forcing it on everyone. In fact, it can be done with Perl 5, as various people have pointed out,

Re: type-checking [Was: What is Perl?]

2000-08-02 Thread Tim Bunce
On Tue, Aug 01, 2000 at 09:25:33PM +, Nick Ing-Simmons wrote: Alan Burlison [EMAIL PROTECTED] writes: No, I disagree. Perl gains a lot of its expressive power from being lax about typing. I suspect it will also impose an unacceptable overhed for the vast majority who don't want it -

Re: type-checking [Was: What is Perl?]

2000-08-02 Thread Tim Bunce
On Tue, Aug 01, 2000 at 10:47:24PM +0100, Alan Burlison wrote: I suspect reorganising the data structures to be cache friendly would gain more benefit than avoiding a few inline bit twiddles. We should do both. Tim.

Re: type-checking [Was: What is Perl?]

2000-08-01 Thread Alan Burlison
Michael Fowler wrote: use typing qw(very-strict); my integer $foo : very-strict = 4; Which would enforce that you can only assign integer constants to $foo (which are seen at compile-time), or other similarly declared integers (or possibly promoted floats, chars, etc. if you

RE: type-checking [Was: What is Perl?]

2000-08-01 Thread Peter Scott
At 02:31 PM 8/1/00 -0700, Tony Payne wrote: No, I disagree. Perl gains a lot of its expressive power from being lax about typing. I suspect it will also impose an unacceptable overhed for the vast majority who don't want it - at the very least every variable access will have to check an

Re: type-checking [Was: What is Perl?]

2000-08-01 Thread Michael Fowler
On Tue, Aug 01, 2000 at 05:31:56PM -0600, Tom Christiansen wrote: Several people have suggested strong typing as a feature, and have been shot down one by one. However, I think it can be done without forcing it on everyone. Can it? Are you prepared to make everyone declare the full,

Re: type-checking [Was: What is Perl?]

2000-08-01 Thread Dan Sugalski
At 09:25 PM 8/1/00 +, Nick Ing-Simmons wrote: Alan Burlison [EMAIL PROTECTED] writes: No, I disagree. Perl gains a lot of its expressive power from being lax about typing. I suspect it will also impose an unacceptable overhed for the vast majority who don't want it - at the very least

Re: type-checking [Was: What is Perl?]

2000-08-01 Thread Nick Ing-Simmons
Alan Burlison [EMAIL PROTECTED] writes: No, I disagree. Perl gains a lot of its expressive power from being lax about typing. I suspect it will also impose an unacceptable overhed for the vast majority who don't want it - at the very least every variable access will have to check an 'are you