view release on metacpan or search on metacpan
0.010   2023-10-29  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...') to follow convention.
0.009   2021-12-03  Released-By: PERLANCAR; Urgency: medium
	  scripts.
0.006   2021-06-01  Released-By: PERLANCAR; Urgency: low
	- No functional changes.
	- Tweak formatting.
0.005   2021-05-09  Released-By: PERLANCAR; Urgency: medium
	- Add entry: App::DiffTarballs.
0.004   2020-02-18  Released-By: PERLANCAR; Urgency: low
	- No functional changes.
	- [dist] Update release note style in Changes.
0.003   2018-12-22  Released-By: PERLANCAR
view release on metacpan or search on metacpan
                            Preamble
  The license agreements of most software companies try to keep users
at the mercy of those companies.  By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  The
General Public License applies to the Free Software Foundation's
software and to any other program whose authors commit to using it.
You can use it for your programs, too.
  When we speak of free software, we are referring to freedom, not
price.  Specifically, the General Public License is designed to make
sure that you have the freedom to give away or sell copies of free
software, that you receive source code or can get it if you want it,
that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
  2. You may modify your copy or copies of the Program or any portion of
it, and copy and distribute such modifications under the terms of Paragraph
1 above, provided that you also do the following:
    a) cause the modified files to carry prominent notices stating that
    you changed the files and the date of any change; and
    b) cause the whole of any work that you distribute or publish, that
    in whole or in part contains the Program or any part thereof, either
    with or without modifications, to be licensed at no charge to all
    third parties under the terms of this General Public License (except
    conditions, and telling the user how to view a copy of this General
    Public License.
    d) You may charge a fee for the physical act of transferring a
    copy, and you may at your option offer warranty protection in
    exchange for a fee.
Mere aggregation of another independent work with the Program (or its
derivative) on a volume of a storage or distribution medium does not bring
the other work under the scope of these terms.
        Appendix: How to Apply These Terms to Your New Programs
  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
2. You may apply bug fixes, portability fixes and other modifications derived
from the Public Domain or from the Copyright Holder. A Package modified in such
a way shall still be considered the Standard Version.
3. You may otherwise modify your copy of this Package in any way, provided that
you insert a prominent notice in each changed file stating how and when you
changed that file, and provided that you do at least ONE of the following:
  a) place your modifications in the Public Domain or otherwise make them
     Freely Available, such as by posting said modifications to Usenet or an
     equivalent medium, or placing the modifications on a major archive site
     such as ftp.uu.net, or by allowing the Copyright Holder to include your
view release on metacpan or search on metacpan
0.002   2023-10-29  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...') to follow convention.
0.001   2019-01-09  Released-By: PERLANCAR
view release on metacpan or search on metacpan
0.002   2023-10-29  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Formatting.
0.001   2023-03-04  Released-By: PERLANCAR
view release on metacpan or search on metacpan
0.003   2023-10-29  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...') to follow convention.
0.002   2020-01-03  Released-By: PERLANCAR; Urgency: medium
view release on metacpan or search on metacpan
0.004   2023-10-29  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...') to follow convention.
0.003   2020-09-21  Released-By: PERLANCAR; Urgency: medium
	- [doc] Add recipe: how to reproduce using lcpan.
0.002   2020-02-18  Released-By: PERLANCAR; Urgency: low
	- No functional changes.
	- [dist] Update release note style in Changes.
0.001   2019-01-09  Released-By: PERLANCAR
view release on metacpan or search on metacpan
lib/Acme/CPANModules/OneLinerTools.pm view on Meta::CPAN
My preference when dumping data structure when debugging Perl application is,
well, Perl format (unlike some others which prefer custom format like
<pm:Data::Printer>). The DD-Dummy distribution provides <pm:DD> module, which in
turn exports `dd` to dump your data structures for debugging using
<pm:Data::Dump>. Another good alternative is <pm:XXX> which by default uses YAML
output but can be changed with this environment variable setting:
    PERL_XXX_DUMPER=Data::Dump
MARKDOWN
            alternate_modules => ['XXX', 'Data::Printer'],
lib/Acme/CPANModules/OneLinerTools.pm view on Meta::CPAN
My preference when dumping data structure when debugging Perl application is,
well, Perl format (unlike some others which prefer custom format like
L<Data::Printer>). The DD-Dummy distribution provides L<DD> module, which in
turn exports C<dd> to dump your data structures for debugging using
L<Data::Dump>. Another good alternative is L<XXX> which by default uses YAML
output but can be changed with this environment variable setting:
 PERL_XXX_DUMPER=Data::Dump
Alternate modules: L<XXX>, L<Data::Printer>
view release on metacpan or search on metacpan
                            Preamble
  The license agreements of most software companies try to keep users
at the mercy of those companies.  By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  The
General Public License applies to the Free Software Foundation's
software and to any other program whose authors commit to using it.
You can use it for your programs, too.
  When we speak of free software, we are referring to freedom, not
price.  Specifically, the General Public License is designed to make
sure that you have the freedom to give away or sell copies of free
software, that you receive source code or can get it if you want it,
that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
  2. You may modify your copy or copies of the Program or any portion of
it, and copy and distribute such modifications under the terms of Paragraph
1 above, provided that you also do the following:
    a) cause the modified files to carry prominent notices stating that
    you changed the files and the date of any change; and
    b) cause the whole of any work that you distribute or publish, that
    in whole or in part contains the Program or any part thereof, either
    with or without modifications, to be licensed at no charge to all
    third parties under the terms of this General Public License (except
    conditions, and telling the user how to view a copy of this General
    Public License.
    d) You may charge a fee for the physical act of transferring a
    copy, and you may at your option offer warranty protection in
    exchange for a fee.
Mere aggregation of another independent work with the Program (or its
derivative) on a volume of a storage or distribution medium does not bring
the other work under the scope of these terms.
        Appendix: How to Apply These Terms to Your New Programs
  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
2. You may apply bug fixes, portability fixes and other modifications
derived from the Public Domain or from the Copyright Holder.  A Package
modified in such a way shall still be considered the Standard Version.
3. You may otherwise modify your copy of this Package in any way, provided
that you insert a prominent notice in each changed file stating how and
when you changed that file, and provided that you do at least ONE of the
following:
    a) place your modifications in the Public Domain or otherwise make them
    Freely Available, such as by posting said modifications to Usenet or
    an equivalent medium, or placing the modifications on a major archive
7. C subroutines (or comparably compiled subroutines in other
languages) supplied by you and linked into this Package in order to
emulate subroutines and variables of the language defined by this
Package shall not be considered part of this Package, but are the
equivalent of input as in Paragraph 6, provided these subroutines do
not change the language in any way that would cause it to fail the
regression tests for the language.
8. Aggregation of this Package with a commercial distribution is always
permitted provided that the use of this Package is embedded; that is,
when no overt attempt is made to make this Package's interfaces visible
view release on metacpan or search on metacpan
        - Add dataset: iterating; add benchmark notes.
0.002   2023-10-05  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - [build] Forgot to add dzil plugin to show images.
0.001   2023-10-05  Released-By: PERLANCAR
view release on metacpan or search on metacpan
                            Preamble
  The license agreements of most software companies try to keep users
at the mercy of those companies.  By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  The
General Public License applies to the Free Software Foundation's
software and to any other program whose authors commit to using it.
You can use it for your programs, too.
  When we speak of free software, we are referring to freedom, not
price.  Specifically, the General Public License is designed to make
sure that you have the freedom to give away or sell copies of free
software, that you receive source code or can get it if you want it,
that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
  2. You may modify your copy or copies of the Program or any portion of
it, and copy and distribute such modifications under the terms of Paragraph
1 above, provided that you also do the following:
    a) cause the modified files to carry prominent notices stating that
    you changed the files and the date of any change; and
    b) cause the whole of any work that you distribute or publish, that
    in whole or in part contains the Program or any part thereof, either
    with or without modifications, to be licensed at no charge to all
    third parties under the terms of this General Public License (except
    conditions, and telling the user how to view a copy of this General
    Public License.
    d) You may charge a fee for the physical act of transferring a
    copy, and you may at your option offer warranty protection in
    exchange for a fee.
Mere aggregation of another independent work with the Program (or its
derivative) on a volume of a storage or distribution medium does not bring
the other work under the scope of these terms.
        Appendix: How to Apply These Terms to Your New Programs
  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
2. You may apply bug fixes, portability fixes and other modifications
derived from the Public Domain or from the Copyright Holder.  A Package
modified in such a way shall still be considered the Standard Version.
3. You may otherwise modify your copy of this Package in any way, provided
that you insert a prominent notice in each changed file stating how and
when you changed that file, and provided that you do at least ONE of the
following:
    a) place your modifications in the Public Domain or otherwise make them
    Freely Available, such as by posting said modifications to Usenet or
    an equivalent medium, or placing the modifications on a major archive
7. C subroutines (or comparably compiled subroutines in other
languages) supplied by you and linked into this Package in order to
emulate subroutines and variables of the language defined by this
Package shall not be considered part of this Package, but are the
equivalent of input as in Paragraph 6, provided these subroutines do
not change the language in any way that would cause it to fail the
regression tests for the language.
8. Aggregation of this Package with a commercial distribution is always
permitted provided that the use of this Package is embedded; that is,
when no overt attempt is made to make this Package's interfaces visible
view release on metacpan or search on metacpan
0.005   2023-10-29  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...') to follow convention.
0.004   2021-05-17  Released-By: PERLANCAR; Urgency: medium
view release on metacpan or search on metacpan
0.002   2023-10-29  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...') to follow convention.
0.001   2021-06-03  Released-By: PERLANCAR
view release on metacpan or search on metacpan
0.003   2023-10-29  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...') to follow convention.
0.002   2021-09-12  Released-By: PERLANCAR; Urgency: medium
view release on metacpan or search on metacpan
0.002   2023-10-31  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...' prefix) to follow convention.
0.001   2021-02-20  Released-By: PERLANCAR
view release on metacpan or search on metacpan
                            Preamble
  The license agreements of most software companies try to keep users
at the mercy of those companies.  By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  The
General Public License applies to the Free Software Foundation's
software and to any other program whose authors commit to using it.
You can use it for your programs, too.
  When we speak of free software, we are referring to freedom, not
price.  Specifically, the General Public License is designed to make
sure that you have the freedom to give away or sell copies of free
software, that you receive source code or can get it if you want it,
that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
  2. You may modify your copy or copies of the Program or any portion of
it, and copy and distribute such modifications under the terms of Paragraph
1 above, provided that you also do the following:
    a) cause the modified files to carry prominent notices stating that
    you changed the files and the date of any change; and
    b) cause the whole of any work that you distribute or publish, that
    in whole or in part contains the Program or any part thereof, either
    with or without modifications, to be licensed at no charge to all
    third parties under the terms of this General Public License (except
    conditions, and telling the user how to view a copy of this General
    Public License.
    d) You may charge a fee for the physical act of transferring a
    copy, and you may at your option offer warranty protection in
    exchange for a fee.
Mere aggregation of another independent work with the Program (or its
derivative) on a volume of a storage or distribution medium does not bring
the other work under the scope of these terms.
        Appendix: How to Apply These Terms to Your New Programs
  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
2. You may apply bug fixes, portability fixes and other modifications derived
from the Public Domain or from the Copyright Holder. A Package modified in such
a way shall still be considered the Standard Version.
3. You may otherwise modify your copy of this Package in any way, provided that
you insert a prominent notice in each changed file stating how and when you
changed that file, and provided that you do at least ONE of the following:
  a) place your modifications in the Public Domain or otherwise make them
     Freely Available, such as by posting said modifications to Usenet or an
     equivalent medium, or placing the modifications on a major archive site
     such as ftp.uu.net, or by allowing the Copyright Holder to include your
view release on metacpan or search on metacpan
                            Preamble
  The license agreements of most software companies try to keep users
at the mercy of those companies.  By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  The
General Public License applies to the Free Software Foundation's
software and to any other program whose authors commit to using it.
You can use it for your programs, too.
  When we speak of free software, we are referring to freedom, not
price.  Specifically, the General Public License is designed to make
sure that you have the freedom to give away or sell copies of free
software, that you receive source code or can get it if you want it,
that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
  2. You may modify your copy or copies of the Program or any portion of
it, and copy and distribute such modifications under the terms of Paragraph
1 above, provided that you also do the following:
    a) cause the modified files to carry prominent notices stating that
    you changed the files and the date of any change; and
    b) cause the whole of any work that you distribute or publish, that
    in whole or in part contains the Program or any part thereof, either
    with or without modifications, to be licensed at no charge to all
    third parties under the terms of this General Public License (except
    conditions, and telling the user how to view a copy of this General
    Public License.
    d) You may charge a fee for the physical act of transferring a
    copy, and you may at your option offer warranty protection in
    exchange for a fee.
Mere aggregation of another independent work with the Program (or its
derivative) on a volume of a storage or distribution medium does not bring
the other work under the scope of these terms.
        Appendix: How to Apply These Terms to Your New Programs
  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
2. You may apply bug fixes, portability fixes and other modifications derived
from the Public Domain or from the Copyright Holder. A Package modified in such
a way shall still be considered the Standard Version.
3. You may otherwise modify your copy of this Package in any way, provided that
you insert a prominent notice in each changed file stating how and when you
changed that file, and provided that you do at least ONE of the following:
  a) place your modifications in the Public Domain or otherwise make them
     Freely Available, such as by posting said modifications to Usenet or an
     equivalent medium, or placing the modifications on a major archive site
     such as ftp.uu.net, or by allowing the Copyright Holder to include your
view release on metacpan or search on metacpan
	- Add Acme::CPAN::Testers::DevelCheckOS.
0.002   2020-10-10  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - [doc] Rebuild with updated POD::Weaver::Plugin::Acme::CPANModules
          (0.005) to tweak generated POD.
view release on metacpan or search on metacpan
                            Preamble
  The license agreements of most software companies try to keep users
at the mercy of those companies.  By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  The
General Public License applies to the Free Software Foundation's
software and to any other program whose authors commit to using it.
You can use it for your programs, too.
  When we speak of free software, we are referring to freedom, not
price.  Specifically, the General Public License is designed to make
sure that you have the freedom to give away or sell copies of free
software, that you receive source code or can get it if you want it,
that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
  2. You may modify your copy or copies of the Program or any portion of
it, and copy and distribute such modifications under the terms of Paragraph
1 above, provided that you also do the following:
    a) cause the modified files to carry prominent notices stating that
    you changed the files and the date of any change; and
    b) cause the whole of any work that you distribute or publish, that
    in whole or in part contains the Program or any part thereof, either
    with or without modifications, to be licensed at no charge to all
    third parties under the terms of this General Public License (except
    conditions, and telling the user how to view a copy of this General
    Public License.
    d) You may charge a fee for the physical act of transferring a
    copy, and you may at your option offer warranty protection in
    exchange for a fee.
Mere aggregation of another independent work with the Program (or its
derivative) on a volume of a storage or distribution medium does not bring
the other work under the scope of these terms.
        Appendix: How to Apply These Terms to Your New Programs
  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
2. You may apply bug fixes, portability fixes and other modifications
derived from the Public Domain or from the Copyright Holder.  A Package
modified in such a way shall still be considered the Standard Version.
3. You may otherwise modify your copy of this Package in any way, provided
that you insert a prominent notice in each changed file stating how and
when you changed that file, and provided that you do at least ONE of the
following:
    a) place your modifications in the Public Domain or otherwise make them
    Freely Available, such as by posting said modifications to Usenet or
    an equivalent medium, or placing the modifications on a major archive
7. C subroutines (or comparably compiled subroutines in other
languages) supplied by you and linked into this Package in order to
emulate subroutines and variables of the language defined by this
Package shall not be considered part of this Package, but are the
equivalent of input as in Paragraph 6, provided these subroutines do
not change the language in any way that would cause it to fail the
regression tests for the language.
8. Aggregation of this Package with a commercial distribution is always
permitted provided that the use of this Package is embedded; that is,
when no overt attempt is made to make this Package's interfaces visible
view release on metacpan or search on metacpan
                            Preamble
  The license agreements of most software companies try to keep users
at the mercy of those companies.  By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  The
General Public License applies to the Free Software Foundation's
software and to any other program whose authors commit to using it.
You can use it for your programs, too.
  When we speak of free software, we are referring to freedom, not
price.  Specifically, the General Public License is designed to make
sure that you have the freedom to give away or sell copies of free
software, that you receive source code or can get it if you want it,
that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
  2. You may modify your copy or copies of the Program or any portion of
it, and copy and distribute such modifications under the terms of Paragraph
1 above, provided that you also do the following:
    a) cause the modified files to carry prominent notices stating that
    you changed the files and the date of any change; and
    b) cause the whole of any work that you distribute or publish, that
    in whole or in part contains the Program or any part thereof, either
    with or without modifications, to be licensed at no charge to all
    third parties under the terms of this General Public License (except
    conditions, and telling the user how to view a copy of this General
    Public License.
    d) You may charge a fee for the physical act of transferring a
    copy, and you may at your option offer warranty protection in
    exchange for a fee.
Mere aggregation of another independent work with the Program (or its
derivative) on a volume of a storage or distribution medium does not bring
the other work under the scope of these terms.
        Appendix: How to Apply These Terms to Your New Programs
  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
2. You may apply bug fixes, portability fixes and other modifications derived
from the Public Domain or from the Copyright Holder. A Package modified in such
a way shall still be considered the Standard Version.
3. You may otherwise modify your copy of this Package in any way, provided that
you insert a prominent notice in each changed file stating how and when you
changed that file, and provided that you do at least ONE of the following:
  a) place your modifications in the Public Domain or otherwise make them
     Freely Available, such as by posting said modifications to Usenet or an
     equivalent medium, or placing the modifications on a major archive site
     such as ftp.uu.net, or by allowing the Copyright Holder to include your
view release on metacpan or search on metacpan
                            Preamble
  The license agreements of most software companies try to keep users
at the mercy of those companies.  By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  The
General Public License applies to the Free Software Foundation's
software and to any other program whose authors commit to using it.
You can use it for your programs, too.
  When we speak of free software, we are referring to freedom, not
price.  Specifically, the General Public License is designed to make
sure that you have the freedom to give away or sell copies of free
software, that you receive source code or can get it if you want it,
that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
  2. You may modify your copy or copies of the Program or any portion of
it, and copy and distribute such modifications under the terms of Paragraph
1 above, provided that you also do the following:
    a) cause the modified files to carry prominent notices stating that
    you changed the files and the date of any change; and
    b) cause the whole of any work that you distribute or publish, that
    in whole or in part contains the Program or any part thereof, either
    with or without modifications, to be licensed at no charge to all
    third parties under the terms of this General Public License (except
    conditions, and telling the user how to view a copy of this General
    Public License.
    d) You may charge a fee for the physical act of transferring a
    copy, and you may at your option offer warranty protection in
    exchange for a fee.
Mere aggregation of another independent work with the Program (or its
derivative) on a volume of a storage or distribution medium does not bring
the other work under the scope of these terms.
        Appendix: How to Apply These Terms to Your New Programs
  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
2. You may apply bug fixes, portability fixes and other modifications derived
from the Public Domain or from the Copyright Holder. A Package modified in such
a way shall still be considered the Standard Version.
3. You may otherwise modify your copy of this Package in any way, provided that
you insert a prominent notice in each changed file stating how and when you
changed that file, and provided that you do at least ONE of the following:
  a) place your modifications in the Public Domain or otherwise make them
     Freely Available, such as by posting said modifications to Usenet or an
     equivalent medium, or placing the modifications on a major archive site
     such as ftp.uu.net, or by allowing the Copyright Holder to include your
view release on metacpan or search on metacpan
0.003   2023-07-06  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - [doc] Rename mentioned Task distribution.
0.002   2023-07-06  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Revise Abstract & Description.
0.001   2023-07-05  Released-By: PERLANCAR
view release on metacpan or search on metacpan
0.002   2023-10-31  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...' prefix) to follow convention.
0.001   2021-09-11  Released-By: PERLANCAR
view release on metacpan or search on metacpan
0.004   2023-10-31  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...' prefix) to follow convention.
0.003   2022-01-21  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Edit Changes entry for 0.002.
0.002   2022-01-17  Released-By: PERLANCAR; Urgency: medium
view release on metacpan or search on metacpan
0.002   2023-10-31  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...' prefix) to follow convention.
0.001   2019-03-10  Released-By: PERLANCAR
view release on metacpan or search on metacpan
0.003   2023-10-31  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...' prefix) to follow convention.
0.002   2021-10-01  Released-By: PERLANCAR; Urgency: medium
view release on metacpan or search on metacpan
0.005   2023-06-20  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract to follow the 'List of modules ...' convention.
0.004   2023-06-20  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - [doc] Mention related list: Acme::CPANModules::Sampling.
0.003   2023-06-20  Released-By: PERLANCAR; Urgency: medium
view release on metacpan or search on metacpan
0.004   2023-06-20  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract to follow the 'List of modules ...' convention.
0.003   2019-11-27  Released-By: PERLANCAR; Urgency: low
	- No functional changes.
	- [doc] Mention Acme::CPANModules::ReadingFilesBackward.
0.002   2019-10-16  Released-By: PERLANCAR; Urgency: low
	- No functional changes.
	- [doc] Mention Acme::CPANModules::PickingRandomItemsFromList.
0.001   2019-01-09  Released-By: PERLANCAR
view release on metacpan or search on metacpan
0.002   2023-10-31  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...' prefix) to follow convention.
0.001   2019-12-26  Released-By: PERLANCAR
view release on metacpan or search on metacpan
        - Add entry: Sub::Fp.
0.003   2023-10-31  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...' prefix) to follow convention.
0.002   2021-03-15  Released-By: PERLANCAR; Urgency: low
	- No functional changes.
	- [doc] Mention some other Acme::CPANModules::PortedFrom::*
	  modules.
view release on metacpan or search on metacpan
0.003   2023-10-31  Released-By: PERLANCAR; Urgency: low
        - No functional changes.
        - Tweak Abstract (add 'List of ...' prefix) to follow convention.
0.002   2021-03-15  Released-By: PERLANCAR; Urgency: low
	- No functional changes.
	- [doc] Mention some other Acme::CPANModules::PortedFrom::*
	  modules.