Virtualmin and Webmin web hosting control panel are written in Perl 5

Subject: Virtualmin and Webmin web hosting control panel are written in Perl 5 Good day from Singapore, I understand that Virtualmin and Webmin web hosting control panel are written in Perl 5. Source: In which perl framework is webmin written into? Link: https://archive.virtualmin.com/node

[Raku/old-design-docs] 63e44c: S22: Clarify how system specific values work and c...

: M S22-package-format.pod Log Message: --- S22: Clarify how system specific values work and correct the list of variables

Re: $? and $! equivalents

On Fri, 14 Sep 2018 18:15:21 -0400 Brandon Allbery wrote: > Magic variables make multiple threads impossible, which is why perl 5 > is stuck with ithreads: what happens if two threads each "run" > something at around the same time? > > In Perl 6, you have a Proc object

Re: $? and $! equivalents

om> wrote: >> >> This is probably going to be a forehead-slapper, but I can't find a >> reference in either perlintro.com or http://docs.perl6.org/ >> (5to6-perlfunc or top-down) for the equivalents of $? and $! in >> P6.What are they? >> >> I wan

Re: $? and $! equivalents

On Fri, Sep 14, 2018 at 5:08 PM Parrot Raiser <1parr...@gmail.com> wrote: > > This is probably going to be a forehead-slapper, but I can't find a > reference in either perlintro.com or http://docs.perl6.org/ > (5to6-perlfunc or top-down) for the equivalents of $? and $

Re: $? and $! equivalents

Magic variables make multiple threads impossible, which is why perl 5 is stuck with ithreads: what happens if two threads each "run" something at around the same time? In Perl 6, you have a Proc object for each subprocess, and can query it for its status and/or result code; for thing

$? and $! equivalents

This is probably going to be a forehead-slapper, but I can't find a reference in either perlintro.com or http://docs.perl6.org/ (5to6-perlfunc or top-down) for the equivalents of $? and $! in P6.What are they? I want to be able to "run" or "shell" programs, then examin

[perl6/specs] 4b8352: Propose tossing %(), @(), and $() magic shortcuts

v6d.pod Log Message: --- Propose tossing %(), @(), and $() magic shortcuts Per https://rt.perl.org/Ticket/Display.html?id=131392

Re: fixing infinities and ranges etc

On 2016-10-30 4:11 PM, Darren Duncan wrote: On 2016-10-30 5:45 AM, yary wrote: Before/AfterEverything are also easy to understand, and would be as natural to use for sorting strings, eg. for saying if a database NULL should go before the empty string or after everything else. On the other hand

Re: fixing infinities and ranges etc

Ranges, is that they are just syntactic alternatives to the Whatever *. They don't seem to be actual typed values that one can say use as declared types for things. Otherwise I like it, and prefer the X::NegInf and X::PosInf,spellings as being easy-to-understand & a good Huffman-e

Re: fixing infinities and ranges etc

I'm not sure I entirely understand the proposal- does it change Inf aka ∞ ? Otherwise I like it, and prefer the X::NegInf and X::PosInf,spellings as being easy-to-understand & a good Huffman-encoding. Before/AfterEverything are also easy to understand, and would be as natural to use fo

fixing infinities and ranges etc

I have observed that the current Perl 6 spec and implementations seem deficient in regards to representing some special values or conditions, in particular the concept of the two linear directional infinities or otherwise special values that naturally sort before and after everything else

[perl6/specs] 2e72b5: Display historical message based on and not...

/perl-with-historical-message.css Log Message: --- Display historical message based on and not Fixes rendering issues on rekonq

[perl6/specs] be783f: prohibit mixing visible and non-visible column sep...

-documentation.pod Log Message: --- prohibit mixing visible and non-visible column separator types in a table Commit: 837c3d8c779575a31df5dc213ef543f0fd372096 https://github.com/perl6/specs/commit/837c3d8c779575a31df5dc213ef543f0fd372096 Author: Tom Browder Date: 2016

[perl6/specs] f8a00d: further amplify table row and cell requirments and...

-documentation.pod Log Message: --- further amplify table row and cell requirments and recommendations Commit: 135839ce478ba2b013c0cb21b9038996dc7f80ea https://github.com/perl6/specs/commit/135839ce478ba2b013c0cb21b9038996dc7f80ea Author: Tom Browder Date: 2016-07-06

[perl6/specs] fd990b: Use less of an eye-bleed color and better position...

/perl-with-historical-message.css Log Message: --- Use less of an eye-bleed color and better positioning for historical message MadcapJake++

Re: Unwanted failure and FAILGOAL

uld be no reason for the parse method to try to match again, and if it fails to test for the end of input. This is not how regexes or grammars work. The + quantifier tries as many times as possible to match the regex. It doesn't look ahead to see if more characters are available, and it d

Re: Unwanted failure and FAILGOAL

tement { 'ID' '=' } rule endvalue { 'keyword' '(' ~ ')' 'pairlist' } *rule unexpected { $ = (\N+) { self.panic($/,"Expected statement but found '$'") }}* In other words: after the statements, we're either at the end of the input, or else we found something unexpected, so capture it and then report it. HTH, Damian

Unwanted failure and FAILGOAL

syntax'. Am I missing something simple here? I would have thought (though this is only a very newbie assumption) that if the end of the input being sent to the grammar has been reached after the last has been matched, then there should be no reason for the parse method to try to

[perl6/specs] fe8f07: spec Channel.fail and Channel.closed

-concurrency.pod Log Message: --- spec Channel.fail and Channel.closed

[perl6/specs] 33eaff: Update Supply introduction and method docs for ser...

-concurrency.pod Log Message: --- Update Supply introduction and method docs for serial supplies Also some Channel clarifications. Commit: cc534c403199b0804fe05bd5cb88676142a878a1 https://github.com/perl6/specs/commit/cc534c403199b0804fe05bd5cb88676142a878a1 Author: skids

Type constraint for named parameters, and questions about 6.c backwards compat

Hello Perl 6 users and developers! I asked this in #perl6, but I wasn't getting a response there, so I figured I would try here. In the following code: > use v6; > > class C { > has Str $!dist-id; > > submethod BUILD(:$!dist-id) {} > } > > my (

Re: Backwards compatibility and release 1.0

On 10/13/2015 03:17 PM, Moritz Lenz wrote: >... We have 390+ modules, and hand-waving away all > trouble of maintaining them seems a bit lofty. > ... a large percentage of the module updates are done by group of > maybe five to a dozen volunteers. ... 5 people updating 70% of 3

Re: Exploit the versioning (was Re: Backwards compatibility and release 1.0)

On 2015-10-15 5:27 AM, yary wrote: Short answer: everything must declare which semantics it expects- everything in Panda/CPAN at least. And we already knew it, just need to do it. I believe this is something Perl 6 should require in general, if it doesn't. That is, it should be MANDATOR

Re: Backwards compatibility and release 1.0

Moritz rant away! Actually, I think this it is a very significant milestone in the development of a language and its ecosystem when backwards compatibility becomes an issue. There will always be modules that have bit rot, insufficient documentation, inadequate testing, no reviews, etc. The

Re: Exploit the versioning (was Re: Backwards compatibility and release 1.0)

Short answer: everything must declare which semantics it expects- everything in Panda/CPAN at least. And we already knew it, just need to do it. Full post: This thread points to a bigger problem, which has a solution that is both cultural and technical. Perl5 has a colossal code corpus, humbling

Re: Backwards compatibility and release 1.0

On 10/15/2015 10:47 AM, Smylers wrote: Moritz Lenz writes: On 10/13/2015 10:52 AM, Richard Hainsworth wrote: Following on the :D not :D thread, something odd stuck out. On 10/13/2015 03:17 PM, Moritz Lenz wrote: We have 390+ modules, and hand-waving away all trouble of maintaining them

Re: Backwards compatibility and release 1.0

> On 15 Oct 2015, at 12:57, Mark Overmeer wrote: > > * Elizabeth Mattijsen (l...@dijkmat.nl) [151015 10:43]: >> FWIW, I’m with FROGGS on this. >> use variables :D; > > In the first response to this message, Moritz spoke about > use invocant :D; > and use pa

Re: Backwards compatibility and release 1.0

* Elizabeth Mattijsen (l...@dijkmat.nl) [151015 10:43]: > FWIW, I’m with FROGGS on this. > use variables :D; In the first response to this message, Moritz spoke about use invocant :D; and use parameters :D; Three different things? > at the top of the scope of your code, and th

Re: Backwards compatibility and release 1.0

>>> >>>> On 10/13/2015 03:17 PM, Moritz Lenz wrote: >>>>> We have 390+ modules, and hand-waving away all trouble of >>>>> maintaining them seems a bit lofty. >>>> Surely, the idea of keeping the release number below 1.0 is to warn

Re: Backwards compatibility and release 1.0

Am 15.10.2015 um 10:47 schrieb Smylers: > Moritz Lenz writes: > >> On 10/13/2015 10:52 AM, Richard Hainsworth wrote: >> >>> Following on the :D not :D thread, something odd stuck out. >>> >>> On 10/13/2015 03:17 PM, Moritz Lenz wrote: >>>&g

Re: Backwards compatibility and release 1.0

Moritz Lenz writes: > On 10/13/2015 10:52 AM, Richard Hainsworth wrote: > > > Following on the :D not :D thread, something odd stuck out. > > > > On 10/13/2015 03:17 PM, Moritz Lenz wrote: > > > > > > We have 390+ modules, and hand-waving away all tro

Re: Exploit the versioning (was Re: Backwards compatibility and release 1.0)

test. If successful, post change. If not, alert a human) I think this can be done, yes, and in principle it would be a good idea. But the problem Moritz seemed to be raising is that each of the Perl 6 modules is possibly in different repositories under a wide variety of users, and

Re: Exploit the versioning (was Re: Backwards compatibility and release 1.0)

Is this particular change one that could be implemented algorithmically, or at least partially so? (E.g. For all modules check for the presence of a ":D". If it's there, no action. If not, insert a line of code. Run a test. If successful, post change. If not, alert a human)

Exploit the versioning (was Re: Backwards compatibility and release 1.0)

I have a proposal. Unlike with say the GLR, perhaps this whole :D thing may be a good test case for the Perl 6 feature of explicit language versioning. How about we don't make the :D change now, and give more thought as to whether we actually want to do it at all. If we do decide

Re: Backwards compatibility and release 1.0

he relatively small number of P6 modules out there, and the enormous impact on the number of bug-reports we will see once Perl6 is out, it may be useful to pull everything "in", into a central archive where a number of people can change everything. Of course, it is not an ideal situation.

Re: Backwards compatibility and release 1.0

pain in the ecosystem. We have 390+ modules, and hand-waving away all trouble of maintaining them seems a bit lofty. Surely, the idea of keeping the release number below 1.0 is to warn early adopter developers that code is subject to change and thus in need of maintenance? It is. But we still

Re: Backwards compatibility and release 1.0

specify, and it doesn't matter about the 390+ modules that exist now. Perl 6 is supposed to be a break it all at once release, and this situation is no different. Having :D being default seems right to me, that would seem to huffman code for the safer behavior which users most likely want by de

Backwards compatibility and release 1.0

Following on the :D not :D thread, something odd stuck out. On 10/13/2015 03:17 PM, Moritz Lenz wrote: But hopefully none of them breaking backwards compatibility on such a large scale. The last few backwards incompatible changes still cause pain in the ecosystem. We have 390+ modules, and

[perl6/specs] f8fc48: problems with grammar attributes and a solution

S12-objects.pod Log Message: --- problems with grammar attributes and a solution One could say one cannot _declare_ grammar attributes but rakudo barks only when we use them. For more context: https://rt.perl.org/Ticket/Display.html?id=122253 http://irclog.perlgeek.de/perl6/2015-03

[perl6/specs] 3cd378: Introduce "api" and :api

: M S11-modules.pod Log Message: --- Introduce "api" and :api

Re: Does Perl 6 use $a and $b in sorting?

sort accepts something callable with an arity of 2. Subroutines, blocks and pointies will do: say sort { $^a cmp $^b }, 5, 3, 2, 6, 4 OUTPUT«(2 3 4 5 6)␤» say sort { $^left cmp $^right }, 5, 3, 2, 6, 4 OUTPUT«(2 3 4 5 6)␤» say sort -> $a, $b { $a cmp $b }, 5, 3, 2, 6, 4 OUTPUT«(2 3 4

Does Perl 6 use $a and $b in sorting?

Because of the the special significance of $a and $b in Perl 5's sort comparison, I always avoid using the names in examples, lest it set a booby-trap for later. I've noticed "a" and "b' being used in some P6 examples. Are they no longer significant, or are they just a poor choice of identifier?

[perl6/specs] 3bf2eb: Fix syntax error and add clarification in S07-list...

S07-lists.pod Log Message: --- Fix syntax error and add clarification in S07-lists

[perl6/specs] c43273: Update .lines and .words more to reality

: M S32-setting-library/IO.pod Log Message: --- Update .lines and .words more to reality

[perl6/specs] 5f132a: Revise and simplify when/default semantics.

: M S04-control.pod Log Message: --- Revise and simplify when/default semantics. This matches behavior seen in implementation and relied upon in the wild. There are various examples of existing code making use of the fact every block has an implicit C<$_>, which it sets so it c

[perl6/specs] 41876e: Add suggestions from nine++ and smls++ (Tuple)

-draft.pod Log Message: --- Add suggestions from nine++ and smls++ (Tuple)

Re: The invocation operators .* and .+

" I need to browse through http://perl6.org/documentation/ for "user docs" showing "why"... and something like your example would be good in a user doc.

Re: The invocation operators .* and .+

* yary [2015-06-17 17:10]: > Perl6's "TEARDOWN" Sorry for the confusion. It’s not in Perl 6. I invented .teardown for this example because I didn’t want to call it .destroy – that’s all. -- Aristotle Pagaltzis //

Re: The invocation operators .* and .+

A couple years ago I wrote a little Perl6 in response to a challenge, and it took me a while to figure out BUILD, BUILDALL, and new(). Learning the object model meant reading what was available on the web plus some time on the #perl6 IRC channel. I managed to get it all working properly for my

Re: The invocation operators .* and .+

it. >> >> Anyplace you would have to say “if you override this method then make >> sure to call the overridden method also” (like calling ->new up the >> inheritance tree). Instead of relying on every subclass writer to not >> screw this up (and leave the object in

Re: The invocation operators .* and .+

lass writer to not screw this up (and leave the object instance in an incoherent state), you use something like these operators to make *sure* a certain method is called all up the inheritance tree as necessary for your de-/init needs. Sorry. Doesn't make sense. class A { sub destroy

Re: The invocation operators .* and .+

Aristotle Pagaltzis writes: > Just because you can’t think of the use of a feature doesn’t mean > there isn’t one. No, though it possibly means the docs could do with a clearer example which demonstrates its use in a situation where it makes sense to use it. Smylers -- http://twitter.com/Smyler

Re: The invocation operators .* and .+

den method also” (like calling ->new up the inheritance tree). Instead of relying on every subclass writer to not screw this up (and leave the object instance in an incoherent state), you use something like these operators to make *sure* a certain method is called all up the inheritance tree as ne

The invocation operators .* and .+

Hi. I know that Perl 6 has a lot of "live and let live" to it, but is it possible somehow to remove features as well? The latest comment about language design by Parrot Raiser (great name!) had me reflect on why I don't use perl any longer, and here is one of the reasons:

[perl6/specs] a62d2c: More GLR discussion, plans, and notes.

-draft.pod Log Message: --- More GLR discussion, plans, and notes.

[perl6/specs] f0dc10: added NPE and rakudobrew spotted on #perl6. fixed ...

S99-glossary.pod Log Message: --- added NPE and rakudobrew spotted on #perl6. fixed a link

[perl6/specs] c9f4f6: added NPE and rakudobrew spotted on #perl6. fixed ...

S99-glossary.pod Log Message: --- added NPE and rakudobrew spotted on #perl6. fixed a link

Re: Synopses size and revision state

f rendering them to dead-tree versions for study. (Personal limitation; I can look up a command definition online, but for study and mental integration, it's got to be something like a real book.) at 4+ lines and 100 lines / page, that would be about 400 pages ? Liz

Re: Synopses size and revision state

#x27;m trying to estimate the cost of rendering them to dead-tree > versions for study. (Personal limitation; I can look up a command > definition online, but for study and mental integration, it's got to > be something like a real book.) at 4+ lines and 100 lines / page, that would be about 400 pages ? Liz

Synopses size and revision state

look up a command definition online, but for study and mental integration, it's got to be something like a real book.)

[perl6/specs] 221b27: typos and whitespace fixes

-glossary.pod Log Message: --- typos and whitespace fixes

[perl6/specs] 6e0869: added MAIN entry and (empty) YOU_ARE_HERE

S99-glossary.pod Log Message: --- added MAIN entry and (empty) YOU_ARE_HERE

[perl6/specs] d92994: be clearer that Terms and Terminators are not ops

-operators.pod Log Message: --- be clearer that Terms and Terminators are not ops

[perl6/specs] c25d86: Update and clarify description of reduce on ops be...

-operators.pod Log Message: --- Update and clarify description of reduce on ops beginning with backslash infix:<\x> was wrongly stated to completely mask triangle reduce with infix:, but we now have the [\[x]] syntax for disambiguation.

[perl6/specs] 3637e6: doc LEXICAL, OUTERS, and CALLERS pseudo packages

-bits.pod Log Message: --- doc LEXICAL, OUTERS, and CALLERS pseudo packages

[perl6/specs] 86d7dd: document .pairup and List.invert

-setting-library/Containers.pod Log Message: --- document .pairup and List.invert

[perl6/specs] 081e2a: document .base and .base-repeatig changes

-setting-library/Numeric.pod Log Message: --- document .base and .base-repeatig changes

[perl6/specs] ca9b96: minor corrections about -e and strictness

-overview.pod M S11-modules.pod M S19-commandline.pod Log Message: --- minor corrections about -e and strictness Now it should be clear that one-liners (-e) are lax by default and that only 'use strict' and 'no strict' have an effect on one-liners and scripts.

[perl6/specs] d25d46: Spec rmpath() and elaborate a bit on move()/.move

: M S16-io.pod Log Message: --- Spec rmpath() and elaborate a bit on move()/.move

[perl6/specs] 518438: laziness and other entries

S99-glossary.pod Log Message: --- laziness and other entries

[perl6/specs] 368ac7: Fix typos and tenses.

-setting-library/IO.pod M S99-glossary.pod Log Message: --- Fix typos and tenses. Commit: 3890f88fbf578943e4310de67789d3df99e7dbbb https://github.com/perl6/specs/commit/3890f88fbf578943e4310de67789d3df99e7dbbb Author: Bruce Gray Date: 2014-12-12 (Fri, 12 Dec 2014

[perl6/specs] f03e92: shortname and longname are compounded already

-glossary.pod Log Message: --- shortname and longname are compounded already

[perl6/specs] f6ea40: [S99] Add long name, short name, and multiple disp...

: M S99-glossary.pod Log Message: --- [S99] Add long name, short name, and multiple dispatch

[perl6/specs] 9f20af: Fix typos and whitespace

-concurrency.pod Log Message: --- Fix typos and whitespace

[perl6/specs] ddb321: Put C<...> around code and type names in S02 and S...

-bits.pod M S03-operators.pod Log Message: --- Put C<...> around code and type names in S02 and S03 Commit: f39433dc61695f967a09b17db6fd64656b4b6e1f https://github.com/perl6/specs/commit/f39433dc61695f967a09b17db6fd64656b4b6e1f Author: Lucas Buchala Date: 2

[perl6/specs] 845eb7: Typos and POD fixes in S02

-bits.pod Log Message: --- Typos and POD fixes in S02

[perl6/specs] d728b4: Don't assume .WHAT and friends are normal

-objects.pod Log Message: --- Don't assume .WHAT and friends are normal Some of them may be implemented as normal methods or operators for now, but we still reserve the right to change any of them into magical ponies.

[perl6/specs] 24850d: Add CONJECTURAL to slip, and ++ version: masak++

: M S04-control.pod Log Message: --- Add CONJECTURAL to slip, and ++ version: masak++

[perl6/specs] ab289f: [S02] Remove '$$' and '@$$' fossils, spotted at #...

-bits.pod Log Message: --- [S02] Remove '$$' and '@$$' fossils, spotted at #apw2014.

[perl6/specs] 37874f: Re-introduce tmpdir() and homedir(), update chdir(...

: M S16-io.pod Log Message: --- Re-introduce tmpdir() and homedir(), update chdir() The original idea behind unifying them into a single chdir() usage, becomes very cumbersome in the implementation. Therefore we're going back to these functions.

Re: state and = vs :=

cases [e.g., flattening vs not flattening]. Reusing existing Perl 5 syntax seemed the most straightforward and intuitive approach.) —and I am debating whether \state $x = \$y should bind only once or every time the surrounding code is executed. I could argue it either way (though I am leaning

Re: state and = vs :=

ould not find a coherent way to handle edge cases [e.g., flattening vs not > flattening]. Reusing existing Perl 5 syntax seemed the most straightforward > and intuitive approach.) > > —and I am debating whether \state $x = \$y should bind only once or every > time the surrounding c

state and = vs :=

straightforward and intuitive approach.) —and I am debating whether \state $x = \$y should bind only once or every time the surrounding code is executed. I could argue it either way (though I am leaning toward the latter), so I thought to find out what Perl 6 does.

[perl6/specs] 59a1d6: Better spec :ENV and :w for Proc::Async.new

: M S17-concurrency.pod Log Message: --- Better spec :ENV and :w for Proc::Async.new

[perl6/specs] a7e69b: FIFO is a queue and LIFO is a stack

-glossary.pod Log Message: --- FIFO is a queue and LIFO is a stack

[perl6/specs] c7f125: relate FIFO and LIFO together

-glossary.pod Log Message: --- relate FIFO and LIFO together

[perl6/specs] fc7aeb: missing plural and period

-glossary.pod Log Message: --- missing plural and period Commit: 0901c85387ac22d181c1b9b3de27e489fc9fe433 https://github.com/perl6/specs/commit/0901c85387ac22d181c1b9b3de27e489fc9fe433 Author: L. Grondin Date: 2014-09-09 (Tue, 09 Sep 2014) Changed paths: M S28

[perl6/specs] 273da4: add tl;dr and TMI

-glossary.pod Log Message: --- add tl;dr and TMI

Re: Grammars and biological data formats

elds, Christopher J wrote: >> Yeah, I'm thinking of a Cat-like class that would chunkify the data and >> check for matches. >> >> The main reason I would like to stick with a consistent grammar-based >> approach is I have seen many instances in BioPerl where a pars

Re: Grammars and biological data formats

On Thu, 14 Aug 2014, Fields, Christopher J wrote: > Yeah, I'm thinking of a Cat-like class that would chunkify the data and check > for matches. > > The main reason I would like to stick with a consistent grammar-based > approach is I have seen many instances in BioPerl wh

Re: Grammars and biological data formats

Yeah, I'm thinking of a Cat-like class that would chunkify the data and check for matches. The main reason I would like to stick with a consistent grammar-based approach is I have seen many instances in BioPerl where a parser is essentially rewritten based on its purpose (full parsing,

Re: Grammars and biological data formats

I was going to pipe in and say that I wouldn't wait around for Cat, I'd write something that reads chunks and then parses that. It'll be a bit more code, but it'll work today. But I see you reached that conclusion already. :) Lately I've found myself writing more and more

Re: Grammars and biological data formats

ented yet >> anywhere. >> >> -- >> Solomon Foster: colo...@gmail.com >> HarmonyWare, Inc: http://www.harmonyware.com > > Yeah, that’s what I recall as well. I see very little in the specs re: Cat > unfortunately. > > chris Ah, nevermind. I did a sea

Re: Grammars and biological data formats

On Aug 13, 2014, at 4:50 AM, Solomon Foster wrote: > On Sat, Aug 9, 2014 at 7:26 PM, Fields, Christopher J > wrote: >> I have a fairly simple question regarding the feasibility of using grammars >> with commonly used biological data formats. >> >> My main question: if I wanted to parse() or su

Re: Grammars and biological data formats

On Sat, Aug 9, 2014 at 7:26 PM, Fields, Christopher J wrote: > I have a fairly simple question regarding the feasibility of using grammars > with commonly used biological data formats. > > My main question: if I wanted to parse() or subparse() vary large files (not > unheard of to have FASTA/FAS

[perl6/specs] b3fceb: lock() is now Lock.new and its methods

: M S29-functions.pod Log Message: --- lock() is now Lock.new and its methods

[perl6/specs] 8b6d0b: Elaborate a bit on exit, END blocks and threads

: M S29-functions.pod Log Message: --- Elaborate a bit on exit, END blocks and threads

[perl6/specs] 43ff89: [S99] Add emptyish lambda and pointy block

: M S99-glossary.pod Log Message: --- [S99] Add emptyish lambda and pointy block

Grammars and biological data formats

/FASTA_format I have a simple grammar here: https://github.com/cjfields/bioperl6/blob/master/lib/Bio/Grammar/Fasta.pm6 and tests here: https://github.com/cjfields/bioperl6/blob/master/t/Grammar/fasta.t Tests pass with the latest Rakudo just fine. chris

  1   2   3   4   5   6   7   8   9   10   >