Author: larry
Date: Fri Feb 16 18:29:45 2007
New Revision: 13589
Modified:
doc/trunk/design/syn/S06.pod
Log:
Clarification on what may be returned from, requested by rhr++
Modified: doc/trunk/design/syn/S06.pod
==
--
From: Larry Wall <[EMAIL PROTECTED]>
Date: Fri, 16 Feb 2007 12:42:27 -0800
. . . so maybe there's some general syntactic relief for rw/ro that is
orthogonal to everything else. But that means it wouldn't be a
trait, a type, a sigil, or a twigil, if it's really orthogonal.
I don'
Author: larry
Date: Fri Feb 16 17:59:34 2007
New Revision: 13588
Modified:
doc/trunk/design/syn/S13.pod
Log:
Clarification of coercion declarations and semantics.
Modified: doc/trunk/design/syn/S13.pod
==
--- doc/tru
On Fri, Feb 16, 2007 at 12:07:43PM -0800, Steve Lukas wrote:
: Larry, Smylers, now I've read your answers.
: Larry, thanks for telling me that it is already specced.
: I have overlooked it, sorry.
: Hello Smylers, thanks for your answer, too. I'm not stucked on
: the form C<$-name>. I am happy to
Larry, Smylers, now I've read your answers.
Larry, thanks for telling me that it is already specced.
I have overlooked it, sorry.
Hello Smylers, thanks for your answer, too. I'm not stucked on
the form C<$-name>. I am happy to get the runtime readonly
or the pragma.
Have a nice day
Stefan
-
Oops, that was a timing problem.
I didn't see that there were answers, sorry.
Kind Regards
Stefan
-
No need to miss a message. Get email on-the-go
with Yahoo! Mail for Mobile. Get started.
Hello Thomas,
thanks for answering.
I fear the C declaration is not suitable
for the purposes I'm thinking of, since it sets
the value at compile time. And at compile time it
can't contact a database, unfortunately.
So, we need the assignment at runtime, but the sanity
check *latest* at comp
Steve Lukas writes:
> (1) The best readable form is probably:
> readonly $temperature; # lexical scope
>
> (2) But this fits better in perl6 conventions:
> my $temperature is ro; # lexical scope
>
> I think form (2) should be possible for variables.
As Larry's pointed out, it pretty much alread
On Fri, Feb 16, 2007 at 04:44:21PM +0100, TSa wrote:
: HaloO,
:
: Steve Lukas wrote:
: >Thinking of the form, I see three ways:
: >(1) The best readable form is probably:
: >readonly $temperature; # lexical scope
:
: The current spec has got
:
:constant $temperature = getValue();
No, that
HaloO,
Steve Lukas wrote:
Thinking of the form, I see three ways:
(1) The best readable form is probably:
readonly $temperature; # lexical scope
The current spec has got
constant $temperature = getValue();
Hope that helps, TSa.
--
Time to start thinking what might make a good Google Summer of Code project.
What would be fun to get paid to work on for 3 months?
Or, what would be useful to encourage someone smart and keen work on for you?
The linked-to page says
We won't start accepting applications until March,
which
# Hello @all,
# I want to suggest readonly or 'is ro' declaration for variables. See:
readonly $temperature = db_temperature_of( $date_time_loc);
...
## much later
# It is *ensured* that $temperature is the original value from database!
my $result = important_decision( $temperature);
#{
It can be
hi,
attached a patch for the PGE implementation of the Lua parser (lua.pg).
fixing:
* make rule match longest identifiers, not keyword-prefixed
identifiers (like "for" in "format")
* fix parameter list rule
* all examples in the lua distribution (in the test directory) can be
parsed correct
hi,
* attached a patch that implements better macro parsing
* begin of better heredoc parsing,but not finished yet.
* added test for macro parsing
regards,
klaas-jan
Index: languages/PIR/examples/macro2.pir
===
--- languages/PIR/ex
14 matches
Mail list logo
