Moritz Lenz wrote in perl.perl6.compiler :
> Hi,
>
> fREW Schmidt wrote:
>> I just threw together a workflow for git with rakudo (
>> http://wiki.github.com/rakudo/rakudo/frews-recommended-workflow) and I think
>> it will help a lot. Hopefully I didn't make any mistakes. Anyway, I plan
>> on tryi
Richard Hainsworth wrote in perl.perl6.language :
> The S16: chown, chmod thread seems to be too unix-focussed.
I was more or less thinking that the syscall-related primitives,
like chown or chmod, could go in a POSIX namespace. Even in UNIX
land nowadays the situation can be much more complex tha
Moritz Lenz wrote in perl.perl6.compiler :
> jerry gay wrote:
>> On Fri, Nov 21, 2008 at 10:43, via RT Moritz Lenz
>> <[EMAIL PROTECTED]> wrote:
>>> # New Ticket Created by Moritz Lenz
>>> # Please include the string: [perl #60732]
>>> # in the subject line of all future correspondence about this
Allison Randal wrote in perl.perl6.internals :
> In the Python test suite, there's a single global location to declare a
> list of test files that are expected to be skipped on a particular
> platform. This has a much cleaner feel than our own motley collection of
> skip and todo markers in vari
David Fetter wrote in perl.perl6.internals :
> Folks,
>
> I've been wrestling with the .spec file to generate RPMs for parrot
> 0.4.12, and so far, the .spec file is winning, so I figured I'd do
> what I always do when I'm losing: fight dirty and call in help :)
I think that Steven Pritchard has w
Smylers wrote in perl.perl6.language :
> Hmmm, a pragma's a bit heavyweight for this; how about being able to set
> this with a special global variable -- that sure sounds handy ...
Actually, in perl 5, $[ *is* a pragma... :)
--
Grepping the source is good for the soul. -- the perldebguts manpag
"Gabor Szabo" wrote in perl.qa :
> While checking if the versions of all the modules are as
> required in our installation I am using the following one liner to
> fetch the version numbers.
>
> perl -MModule -e'print $Module::VERSION'
You should probably use -mModule to avoid calling Module::impor
"Michael G Schwern" wrote in perl.qa :
> * What about Test::Harness?
>
> Test::Harness remains its own thing.
>
> At some point in the future Test::Harness will likely be gutted and
> turned into a thin wrapper around TAP::Harness. I'm not caring about
> this right now.
What about prove(1) ? Are
Ovid wrote in perl.qa :
>
> You've run into a problem which surprises a few folks but definitely
> causes problems. In a nutshell, use_ok internally traps the "use"
> call with an eval. However, even if it fails (as in your case), the
> bytecode might still be compiled and in memory and, as a res
Andy Lester wrote:
> I'm approaching the end of this release cycle. I really want to get
> this released.
>
> I've removed the meaningless percentages of tests that have failed.
> If you rely on the output at the end, it's different now.
I'm not attached to percentages, which I wasn't looki
On 23/04/06, Steve Peters <[EMAIL PROTECTED]> wrote:
What's happening above is that TEST cannot handle seeing tests come in
out of order, while harness can. I'm scanning Test::Harness::TAP a bit,
but it seems to be unspecified whether this is OK or not. Should TEST
care if the tests are reported
Andy Lester wrote in perl.qa :
> Please try out this dev release. I'd like to make it 2.58 tomorrow.
Now integrated into bleadperl, all tests pass here.
--
* What system had proved more effective?
* Indirect suggestion implicating selfinterest.
-- Ulysses
Andy Lester wrote in perl.qa :
> On Mon, Oct 10, 2005 at 02:52:49PM -0700, chromatic ([EMAIL PROTECTED]) wrote:
>> > I do NOT want to see that sort of thing as patches to Test::Harness.
>
>> I have a few ideas myself on how to make T::H a little more clean and
>> useful, but I'd have to do some ref
Brent 'Dax' Royal-Gordon wrote in perl.perl6.language :
>
> I would like "is sensitive" to be defined to mean that any data stored
> in that variable, at any level of recursion, will be zeroed out as
> soon as it is garbage collected. Particular implementations can add
> extra features on top of t
Brent 'Dax' Royal-Gordon wrote in perl.perl6.language :
> Basically, I'd like to be able to mark a variable as "sensitive" or
> "secret". This implies that the language should overwrite the memory
> it uses before deallocating it, and that if possible it should tell
> the virtual memory system to
I just commited into bleadperl a patch that implements this :
$ ./perl -e 'no 5'
Perls since v5.0.0 too modern--this is v5.9.3, stopped at -e line 1.
BEGIN failed--compilation aborted at -e line 1.
That is, the exact opposite of the current "use VERSION" syntax.
One of the uses I had
On 7/4/05, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> I'm going through some work to restore Test::More and Test::Harness to work
> on 5.4.5, minor stuff really, and I'm wondering if its worth the trouble.
>
> Has anyone seen 5.004_xx in the wild? And if so, were people actively
> developing
Autrijus Tang wrote in perl.perl6.language :
>
> 4. Software Transaction Memory
>
> Like GHC Haskell, Fortress introduces the `atomic` operator that takes a
> block, and ensures that any code running inside the block, in a
> concurrent setting, must happen transactionally -- i.e. if some
> precondi
Michael G Schwern wrote in perl.qa :
> On Mon, Apr 18, 2005 at 05:03:42PM +0100, David Cantrell wrote:
>> 1) Am I correct to seperate the package version (1.3004) from the
A small correction -- 1.3004 would be the distribution version, (not
mentioned as $...::VERSION in any package).
Aaron Sherman wrote in perl.perl6.language :
>
> A silly question: is there a canonical character set from which we
> extract these ranges? Are we hard-coding Unicode here, or is there some
> way for the user to specify the character set for ranges?
Perl 5 forces [a-z] (or [i-j] for that matter) t
This one fixes "make test", by forcing the fix of "test" target of the
generated Makefile. I'd rather have Ingy reviewing it or something,
because AFAICT it's his territory -- dark makemaker places where black
magic hides behind obscure curtains. ("make install" still works and
still installs every
This fixes installing to a different DESTDIR.
Index: Makefile.PL
===
--- Makefile.PL (revision 1233)
+++ Makefile.PL (working copy)
@@ -105,10 +105,10 @@
pure_site_install ::
\$(NOECHO) \$(MOD_INSTALL) \\
- \
Markus Laire wrote in perl.perl6.compiler :
>> my $use_debug_mode = BEGIN { %*ENV{DEBUGME} ?? 1 :: 0 };
>
> According to S04 you'd use INIT block for that. INIT is run at run time,
> ASAP. But BEGIN is run at compile time, ASAP.
Fair enough, makes sense. As long as BEGIN and CHECK blocks are
Autrijus Tang wrote in perl.perl6.compiler :
> Consider this program, example.p6:
>
> use v6;
> my $var = BEGIN { say "I'm compiling, man"; time() }
> say "Compiled at { time() - $var } seconds ago!";
>
> Is this behaviour correct?
>
> % pugscc --parrot example.p6
> I'm compilin
Aaron Sherman wrote in perl.perl6.compiler :
> On Wed, 2005-02-23 at 07:43 -0500, Aaron Sherman wrote:
>> has anyone considered petitioning the major Linux distribution vendors
>> to include it in their upcoming releases?
> [...]
>> I don't know anything about Haskell, and it would be presumptuous
Autrijus Tang wrote:
> jn Tue, Feb 22, 2005 at 10:54:26AM -0000, Rafael Garcia-Suarez wrote:
> > I had this silly idea, to try to add %ENV to pugs. That would be an
> > interesting exercise. So I can write CGI scripts. Maybe. But I don't
> > know what's the Right wa
I had this silly idea, to try to add %ENV to pugs. That would be an
interesting exercise. So I can write CGI scripts. Maybe. But I don't
know what's the Right way to do it in Perl 6. Any hints ?
--
#!/usr/bin/pugs
say "Just another Pugs hacker";
Michael G Schwern wrote:
> http://svn.schwern.org/svn/CPAN/Test-Simple/trunk
> or
> svn://svn.schwern.org/CPAN/Test-Simple/trunk
> or
> http://www.pobox.com/~schwern/src/Test-Simple-0.54.tar.gz
> or
> a CPAN near you.
Thanks, bleadperl upgraded (as change #23654).
David Wheeler wrote in perl.qa :
>> Test::LongString is one of those modules that you should be using if
>> you're doing testing against large data elements, especially web pages.
>> There are now examples in the docs that I hope make you say "Wow, this
>> is cool, thanks RGS!"
>
> I use Text::Diff
On Fri, 3 Sep 2004 11:41:05 +0100, Tim Bunce <[EMAIL PROTECTED]> wrote:
> Is there some syntax to express if the struct is packed or
> needs alignment? (Perhaps that would be needed per element.)
Why am I suddenly thinking about unions ?
Andrew Pimlott wrote:
>
> Can you tell me where this limitation in perl threads is documented?
> Is there any hope that it will be removed in the future?
It's not a limitation, if you share a hash it looks normal to me
that you should share its elements too. (or you end up with weird
quantum hash
Andrew Pimlott wrote:
> I got this error, which I traced down to accidentally calling is() with
> a hashref as the third argument, where the name should have been:
>
> use Test::More 'no_plan';
> is(1,1,{});
Autrijus has fixed this bug in bleadperl, see the patch at
http://public.act
[EMAIL PROTECTED] wrote:
>
> 04pause.html has some useful and important information people should
> probably read before requesting an account.
It's also linked from http://pause.perl.org/ ("about PAUSE"); this
latest URL is probably easier to remember.
Kirrily Skud Robert wrote:
> Here's an initial patch to perlnewmod, the main points of which are:
>
> * recommend module-starter over h2xs
> * modernise recommended h2xs invocation
> * modernise list of recommended modules to learn from
> * refer to Test::Simple and Test::More instead of Test
> *
Andy Lester wrote:
> Here's a test file that makes sure that even with sub q{}, that q() is
> an operator, but &q() and main::q() are function calls. I suggest that
> it be called t/comp/operator-subs.t.
Thanks, applied as #23215.
> #./perl -T
^^
the lack of "!" here gave me a small headache d
Andy Lester wrote:
> t/op/sleep.t doesn't actually check to see how long it's slept for. The
> test takes sleep()'s word for it.
>
> I also modernized it to use Test::More and its convenience functions.
Thanks, applied as change 23206.
Andy Lester wrote:
> Lets you check the dollar vars of your results
>
> matches_are( "dog food", qr/dog(.+)/, 1=>"food", "Matched OK" );
>
> or
>
> matches_are( "first middle end", qr/middle|center/,
> "&" => "middle", "`" => "first " );
>
> Eventually we'll handle the punc vars
Michele Dondi wrote:
> I must say I've still not read all apocalypses, and OTOH I suspect that
> this could be done more or less easily with a custom function (provided
> that variables will have a method to keep track of their history, or, more
> reasonably, will be *allowed* to have it), but I wo
Luke Palmer wrote:
> That left recursion won't do. I can't remember my transformation rules
> well enough to know how to put that in a form suitable for a recursive
> descent parser. To be honest, I've never seen an RPN calculator modeled
> with a grammar.
Well, the main advantage of an RPM synt
Sean O'Rourke wrote:
> * To really show where P6 rocks, you need to show dynamic features. A
> simple example might be using a language with keywords kept in
> variables, allowing you change between e.g. "for, while, if", "pour,
> tandis-que, si", etc.
Small correction : "pour, tant_que, si
Luke Palmer wrote:
> Also, if this is going to be an explanation rather than just a picture,
> I suggest you go with Perl's usual versatile power, and store the
> operators in a declarative data source.
>
> grammar RPN {
> my @operator = << + - * / >>;
>
> rule input { * }
>
Jim Cromie wrote:
> Jim Cromie wrote:
>
> > folks,
> >
> > attached patch has following adjustments to B::Concise and its tests.
>
>
> heres 2nd rev of that patch, now against 22802
Thanks, applied as change 22820. Time to play with it...
Aaron Sherman wrote:
> Is it a special type of calling convention, e.g.:
>
> sub s (Regex $pat, Str $replace, bool ?$i) is doublequotelike returns(Str) {
Ooh, "doublequotelike" sounds so much 1984.
(Moreover it doesn't describe accurately the reality, which allows to
use different delimiter
Jim Cromie wrote:
>
> Heres a 'working' version of my earlier proposal,
> patched against [EMAIL PROTECTED]
>
> I hope you find it useful for regression testing of the optimizer,
> and the opcode generation phases.
Thanks, applied to bleadperl as change #22664.
Larry Wall wrote in perl.perl6.internals :
> Do bear in mind that Perl can execute bits of code as it's compiling,
> so if a bit of code is untrustworthy, you shouldn't be compiling it
> in the first place, unless you've prescanned it to reject C,
> C, and other macro definitions, or (more usefully
Dan Sugalski wrote in perl.perl6.internals :
> At 2:50 PM +0100 3/24/04, Leopold Toetsch wrote:
>>Dan Sugalski <[EMAIL PROTECTED]> wrote:
>>
>>> At any rate, perl 5's Safe module is a good example of the Wrong Way
>>> to do security, and as such we're going to take it as a cautionary
>>> tale ra
Andy Wardley wrote in perl.perl6.language :
> I'm so happy! I just found out, totally by accident, that I can type
> the « and » characters by pressing AltGr + Z and AltGr + X,
> respectively.
Of course this information is almost completely unusable without knowing
your OS, your locale, and you
Dan Sugalski wrote in perl.perl6.internals :
>
> This seems... too simple, so I'm sure I'm missing something besides
> the potential massive memory usage. So, by all means, have at it.
You'll need to worry about actions that invalidate all or part of the
method cache : introduction of a new clas
Larry Wall wrote in perl.perl6.internals :
>
> Not using metaconfig (or something like it) would be the biggest
> mistake. It's actually next to impossible to maintain something like
> a Configure script directly.
Actually as parrot already uses IIUC variables set up by Configure,
I think one co
Damian Conway wrote in perl.perl6.language :
>
> I'd favour UNITCHECK and CHECK, mainly for the greater compatibility with
> Perl 5 and with software engineering jargon.
As far as Perl 5 is concerned, it appears that most people who write
CHECK mean UNITCHECK. Including you :)
> And because MAIN
Larry Wall wrote in perl.perl6.language :
>
> Possibly a CHECK block that is compiled after end of main compilation
> should translate itself to a UNITCHECK. But maybe it should be an error.
>
> But it's also possible that CHECK should mean "unit check", and
> there should be an explicit MAINCHE
Larry Wall wrote in perl.perl6.language :
>: In perl 5 those blocks are executed at the
>: transition between the compilation and the execution phase *of the main
>: program*. This is convenient for some purposes (the O and B::* modules)
>: and inconvient for others (Attribute::Handlers, etc. etc.)
Larry Wall wrote in perl.perl6.language :
>
> In theory, yes, if you ask it to check in a CHECK block, and if you're
> willing for the check to assume that no eval or INIT block is going
> to supply the missing sub before it's actually called, and that no
> run-time code is going to alias the sub
Jerome Quelin wrote in perl.perl6.internals :
>
> But what should those addresses do when receiving a message?
> - parrotbug: should open a RT ticket?
> - status-ok: ?
> - status-nok: should open a RT ticket?
Excuse me from stepping in, but I don't see why three adresses are
necessary. From my (l
Jim Cromie wrote:
> >ok() goes to stdout by default, diag() to stderr
> >
>
> which is, I presume, why perl -Ilib t/foo.t produces more output than
> make test.
> I see that as a feature.I guess note() should go to stderr - for my
> preferences at least.
Then just do *note = \&diag :)
> >
Jim Cromie wrote:
>
> Well, it seems Ive been abusing diag() for some time now :-O
>
> Is there a 'right' way to do this ? perhaps just using ok() ?
ok() goes to stdout by default, diag() to stderr
> or maybe a new function, ex: note() is better:
>
> note.
Andrew Potozniak wrote in perl.qa :
> I was wondering if there was anything built in Perl (a Module) that
> will take in a Perl file and parse that into an abstract or concrete syntax
> tree. I searched around cpan for a bit and couldn't find what I was looking
> for. If anyone is wondering
Larry Wall wrote in perl.perl6.language :
> On Wed, Dec 17, 2003 at 12:11:59AM +, Piers Cawley wrote:
>: When you say CHECK time, do you mean there'll be a CHECK phase for
>: code that gets required at run time?
>
> Dunno about that. When I say CHECK time I'm primarily referring
> to the end
Andy Lester wrote in perl.qa :
>> prove begins with #!/usr/bin/perl and prove-switches.t
>> runs it with
>> my @actual = qx/$prove -Ifirst -D -I second -Ithird -Tvdb/;
>> A $^X should be inserted here.
>> (in bleadperl, the shebang line of prove is fixed when installed.)
>
> What should be in
H.Merijn Brand wrote:
> t/prove-switchesPerl lib version (v5.6.1) doesn't match executable version
> (v5.8.0) at /pro/lib/perl5/5.6.1/PA-RISC2.0/Config.pm line 21.
prove begins with #!/usr/bin/perl and prove-switches.t
runs it with
my @actual = qx/$prove -Ifirst -D -I second -Ithird -Tvdb
Andy Lester wrote:
>
> > How am I going to test this ?
>
> Take a look at Test::Warn for warnings, and Test::Exception for errors.
>
> I think qa.perl.org needs a listing of Test::* modules so that people
> know what's available.
http://search.cpan.org/search?query=Test-&mode=dist
lists many o
Potozniak, Andrew wrote:
>
> Is anyone going to develop this, or is all of this just
> wishfull/theorhetical thinking? If someone will develop this are we going
> to add it to Test::More or create a module wrapped around Test::More with
> the added functionality?
What is "this" feature you're re
FWIW, I uploaded Test::LongString 0.03 to CPAN. It implements
like_string() and unlike_string(), and also :
> (That's why I can imagine accepting the default length as an argument
> to Test::LongString::import().)
Chromatic wrote in perl.qa :
> On Mon, 2003-11-17 at 06:54, Potozniak, Andrew wrote:
>
>> What's stopping you from creating this global var
>> and passing it in to the function whenever it is called?
>
> Good taste. If it's going to be more convenient than Test::More's
> like(), go all the way a
Potozniak, Andrew wrote:
>
> I would suggest something along the lines of:
>
> &like_html(actual_value, expected_regex, max_chars_to_output,
> string_description);
In fact I think that making max_chars_to_output a global configuration
variable is a better option, because repeating it (if yo
Mark Stosberg wrote in perl.qa :
> I'm frequently using 'like' to test $agent->content against a regular
> expression.
>
> When I have a lot of these in a new test script and they are all
> failing, I get a boatload of HTML source floating by, which
> makes it tedious at times to find out what a
Elizabeth Mattijsen wrote:
> Just wondering, is keys() optimized for void context? Perlfunc only states:
>
> As a side effect, calling keys() resets the HASHâ¤_s internal iterator...
Yes, it is.
> If keys() _is_ optimized for void context, a change in the
> perlfunc.pod seems to be in orde
Andrew Savige wrote in perl-qa :
>
> Given the differences in behaviour with taint mode, it seems to me
> that for a "taint mode test" (i.e. one with -wT in its first line)
> Test::Harness should run the test twice -- once with taint mode and
> once without. Though I suppose there might be a case
Thomas Klausner wrote in perl.qa :
>
> Well, here's a list of lowercase dist on CPAN (238 dists). Quite a lot of
> those are in fact real distributions (eg. perl, parrot). In fact I think
> that perl itself shouldn't be part of CPANTS
>
> I've no clue on how to figure out if something is a pragm
Chromatic wrote in perl.qa :
>
> Stuff in t/op mostly can't use Test or Test::More because those modules
> rely on the features being tested. Most everything else can use
> Test::More. Barring any Unicode-related fiascos (of which I am proudly
> and blissfully unaware), they probably haven't bee
Michael G Schwern wrote in perl.qa :
> This all suggests another check: stray files. Emacs backup files. CVS
> directories. Empty directories. #...# backup files. Makefiles shipped
> with Makefile.PL, Build and _build shipped with Build.PL, blib/...
In other words, the contents of the default
Nick Ing-Simmons <[EMAIL PROTECTED]> wrote:
> >Could we infer that a distribution that comes with several Makefile.PLs
> >may have an overcomplicated build process, maybe indicating a low
> >kwalitee ?
>
> Should I infer that to get Tk's kwalitee up it should build as a
> one monolithic .so ?
I
Thomas Klausner wrote:
> there are currently 4 dists on CPAN that only include a configure script
> (makepp-1.19, glist-0.9.17a10, swig1.1p5, shufflestat-0.0.3)
>
> 179 do not include any of Makefile.PL, Build.PL or configure.
>
> Quite a lot come with two or three of those files.
Could we infe
Thomas Klausner wrote in perl.qa :
>
> Hints that were in Leon's last release, but which I didn't port up to now:
> * POD errors
> * POD/Code ratio (what would be a good measurement?)
use Pod::Coverage ?
> * testers results
> * number of releases
Folks,
I've added and integrated a bunch of Test::* modules from bleadperl to
5.6.2. I've also roughly modernized the scripts t/TEST and t/harness
with the bleadperl version, so that all *.t files are found, etc. Now if
you're aware of a difference between bleadperl and CPAN or something, or
if you
Andrew savige wrote in perl.qa :
> Running variants of:
>
> tar tzf perl-5.8.0.tar.gz | perl -lne'print if tr|-_./a-zA-Z0-9||c'
>
> suggests only [-_./a-zA-Z0-9] are valid characters in a path name.
>
> Then I noticed 'perldoc perlport' lists the portable filename
> characters as defined by ANSI
Michael G Schwern wrote in perl.qa :
> http://www.pobox.com/~schwern/cgi-bin/perl-qa-wiki.cgi
Do you want a link to this from qa.perl.org ?
david nicol wrote:
> [EMAIL PROTECTED] perl -le '$_{a}=27; package notmain; print $_{a}'
> 27
>
> Gosh!
>
> Let's document it! Would it go in perlvar or perlsyn?
It's already documented, in perlvar/"Technical Note on the Syntax of Variable Names"
(at the end)
Piers Cawley wrote in perl.perl6.internals :
> I want a Ponie!
> I promise that, as development of Ponie (the port of Perl 5 to Parrot)
> accelerates you'll see a summary of Ponie activity in this summary as
> well.
In fact I imagined I was more or less going to do this, based on
imagi
Michael G Schwern wrote in perl.qa :
> The only part missing is the ability to shut the tests off once you've
> released it to production.
You could perhaps use the assertion feature of perl >= 5.9.0
(assertion.pm and -A switch -- yes I know it lacks docs.)
Robert Spier wrote in perl.perl6.internals :
>
> A lot of projects have a "HACKING" file that explains "ground rules"
> for contributing to the project -- all in one place. (Or at least it
> references where things are.)
I'd love to see a file like this in parrot.
Perl 5 provides pod/perlhack.po
chromatic wrote in perl.qa :
> One idea is attaching a simple test case to every bug report that
> doesn't have test code that's nearly right for the core. It's a lot
> easier to touch up a test case than it is to write one, so we could do
> a lot of good by turning bug reports into executable
Alan Burlison wrote in perl.perl6.internals :
> Piers Cawley wrote:
>
>> Small Perl task for the interested
>> Want to get involved in the Parrot development process? Don't know much
>> about Virtual Machine design and implementation? Do know Perl? Dan has a
>> small but interesting
Jonathan Scott Duff wrote in perl.perl6.language :
>
> My only dream is that by this time next year we have a fully-
> functional-people-can-use-it-in-production Perl6. It doesn't even
> have to be 100% complete; I think just 85% would be enough if it were
> the right 85%.
20% would be enough if
Michael G Schwern wrote in perl.qa :
> On Tue, Jun 24, 2003 at 02:04:25PM -0500, Andy Lester wrote:
>> All this "make sure no warnings fired" is good thinking. But why not
>> roll it into Test::Harness, and make it switch selectable? It's
>> really T::H that we want keeping an eye on this, righ
Michael G Schwern wrote in perl.qa :
> On Tue, Jun 24, 2003 at 01:36:52PM +0200, Rafael Garcia-Suarez wrote:
>> BTW, what about modules that define their own category of warnings
>> (via warnings::register) ? It'd be useful to have a module to ease
>> testing for wa
Fergal Daly wrote:
>
> Also how about calling it Test::Warn::Auto? I'm not particularly happy with
> None,
+1 for ::Auto.
BTW, what about modules that define their own category of warnings
(via warnings::register) ? It'd be useful to have a module to ease
testing for warnings presence/absence o
Nicholas Clark wrote:
>
> class Foo {
> ...
> std::size_t spare = 0
> std::size_t allocate = 4096
> std::size_t min_readline = 80
>
> and have the compiler know that if I specify a member initialiser in my
> my constructor, then that should be used, otherwise to default to using
>
Andy Wardley wrote:
>
> If my understanding of the design of Perl 6 is correct, the lexer, parser
> and any other related components will be highly configurable and/or
> replaceable. The goal is to provide support for "little languages" by
> separating Perl the language from perl the interpreter
Nicholas Clark wrote in perl.perl6.internals :
>
>> > r->score = r->use_count + (r->lhs_use_count << 2);
>> >
>> >r->score += 1 << (loop_depth * 3);
[...]
> I wonder how hard it would be to make a --fsummon-nasal-demons flag for gcc
> that added trap code for all classes of undefined behavi
Dan Sugalski wrote in perl.perl6.internals :
>
> In Perl terms, assume we have a method PRE that gets called before
> any method in a class is called, and AUTOLOAD which is called if you
> call a method on a class and that method doesn't exist. Does AUTOLOAD
> have to get called to check for PR
Joseph F. Ryan wrote in perl.perl6.language :
>
> If the final design stays the way it is now, there really won't be
> a "lexer". Instead, a perl6 grammar parses the data, and builds up
> a huge match-object as it, well, matches. This match object is then
> munged into the optree.
Oh, yes, I re
Joseph F. Ryan wrote in perl.perl6.language :
>
> I think the point of having C as a sub rather than as a separate
> syntax is so the parser doesn't have to do anything special for
> special keywords.
>
> I think the goal was to simplify the compiler, but with the
> discussion of recent weeks, it
Brent Dax wrote in perl.perl6.language :
> Yes, I know this means that we have 'else if' instead of 'elsif', but
> it's only two more characters and it makes the grammar cleaner.
The tokeniser could send two tokens "else" and "if" whenever it
recognizes the keyword "elsif" -- so this isn't a probl
Dan Sugalski <[EMAIL PROTECTED]> wrote:
>
> And keyboards, don't forget keyboards. These pesky primitive ones we
> have now would require a lot of shift-control-alt-meta-cokebottle key
> sequences...
And vt100 consoles ! There are still sysadmins that struggle with a buggy
perl script, having r
John Siracusa <[EMAIL PROTECTED]> wrote:
>
> Well, er, don't we need to decide what the subroutine attribute is, so that
> the compiler will know to honor it and make the code "disappear"? It
> doesn't seem like a feature that can be added from "userland" after the fact
> (but maybe I'm wrong...)
Dave Whipp wrote in perl.perl6.language :
> But with the different precedence. At last, I can assign from a list without
> using parentheses:
>
> @a = 1, 2, 3; # newbie error
> @a <~ 1, 2, 3; # would work
or :
@a <~ 1 <~ 2 <~ 3;
or :
1, 2, 3 ~> @a;
which would be also written as :
Nicholas Clark wrote in perl.perl6.language :
>> Actually I don't think you can define a grammar where two operators have
>> the same precedence but different associativity. Be it a pure BNF
>> grammar, or a classical yacc specification (using the %left and %right
>> declarations).
>
> But that wo
Luke Palmer <[EMAIL PROTECTED]> wrote:
>
> Not necessarily. <~ will necessarily need to be right-associative,
> while ~> left, however.
Not sure if you aren't getting this backwards, but anyway I often find
myself confused with right and left.
> It would be logical to give them the same
> prece
frederic fabbro <[EMAIL PROTECTED]> wrote:
>
> Can one see it as a shell redirection/pipe? This may sound funny,
> but is the following ok?
>@b <~ @a ~> @c; # @c = @b = @a;
> (@b <~ @a) ~> @c; # same order i guess
>
> so one can also:
> @keep <~ grep /good/ <~ @list ~> gre
1 - 100 of 124 matches
Mail list logo
