Brent Dax [EMAIL PROTECTED] writes:
Garrett Goebel:
# my int ($pre, $in, $post) is constant = (0..2);
#
# Means that you are asking for compile time optimizations, and
# agreeing not
# to bless references to, or ascribe run-time properties to
# those scalars. So
# we've already got
On Thu, Nov 01, 2001 at 10:13:22PM -0500, Ken Fox wrote:
On the other hand, people live with C's preprocessor
and its #undef/#define of constants. If C programmers
don't mind having different parts of a program compiled
with different values for the same constant, then why
should Perl
From: Ken Fox [mailto:[EMAIL PROTECTED]]
Here in the 10-step Perl 6 program we don't talk about
resolution. We just learn to cope with change. ;)
;) I'm still working to grok the changes. I thought I was getting generally
clued in after reading the Apocalypses/Exegesises... but discussions on
On Thu, 1 Nov 2001, Garrett Goebel wrote:
On Wed, 31 Oct 2001, David Nesting wrote:
On Tue, Oct 30, 2001 at 09:37:39AM -0500, Aaron Sherman wrote:
: Yep, but in Perl5, this was never very clean or obvious to the
: casual programmer. Constants have been coming of age in Perl,
: and
From: David M. Lloyd [mailto:[EMAIL PROTECTED]]
On Thu, 1 Nov 2001, Garrett Goebel wrote:
On Wed, 31 Oct 2001, David Nesting wrote:
On Tue, Oct 30, 2001, Aaron Sherman wrote:
: Yep, but in Perl5, this was never very clean or obvious
: to the casual programmer. Constants have been
Garrett Goebel:
# my int ($pre, $in, $post) is constant = (0..2);
#
# Means that you are asking for compile time optimizations, and
# agreeing not
# to bless references to, or ascribe run-time properties to
# those scalars. So
# we've already got variables with constant values.
#
# I guess my
Garrett Goebel wrote:
worried about the loss of data-hiding with Perl6's lexicals.
Was that ever resolved?
Here in the 10-step Perl 6 program we don't talk about
resolution. We just learn to cope with change. ;)
There were two issues I had. As a Perl 6 user I felt
uncomfortable that Perl 6 is
