RE: Two questions on Perl 6 functionality

[Timothy S. Nelson]

On Sun, 20 Jun 2010, Xi Yang wrote:



You might mis-understood method modifiers. I mean:
before x()
after x()
around x()
.


	Just a note that I've usually seen this called Aspect-Oriented 
Programming.



2: Does Perl 6 has build-in support for message passing (like those in Glib and 
Actionscript)?


I fear I'm not qualified to answer that, and I hope somebody else picks
up the topic.


	I'm even less qualified, but I have this feeling that the whole thing 
is tied up in the event/threading side of things.  But I don't actually know 
anything.


	Xi, basically, the specification for Events and Threading is still 
very much in its draft stages:


http://perlcabal.org/syn/S17.html

	You can see that it mentions an Event Loop, but there's no information 
about it yet.  So assuming that I'm correct, the best answer we can give you 
is The plans for that part of Perl 6 are still on the drawing board.


HTH,

:)


-
| Name: Tim Nelson | Because the Creator is,|
| E-mail: wayl...@wayland.id.au| I am   |
-

BEGIN GEEK CODE BLOCK
Version 3.12
GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V- 
PE(+) Y+++ PGP-+++ R(+) !tv b++ DI D G+ e++ h! y-

-END GEEK CODE BLOCK-

Re: very basic type checking

[Darren Duncan]

Moritz Lenz wrote:
But I fear that optimizations are a risky business, considering our 
rather low test coverage (and considering that we don't really know how 
much of our code paths are actually covered by tests).


In that case, perhaps Rakudo should have a config or compile-time (of Rakudo 
itself) option where it can be run either without or with any compile-time 
optimizations, where said optimizations have any changing the runtime behavior. 
 This being under the assumption that a Rakudo codebase that doesn't support 
the optimizations is simpler and easier to prove correct or debug than one with 
them.  Users suspecting a bug when they run with the optimizations could rerun 
without them to see if there's a difference.


This idea isn't without precedent.  I believe that Parrot has long had multiple 
run cores, such as ones with JIT or certain optimizations versus ones without. 
Or maybe this was an early development that later went away?


-- Darren Duncan