"Fossies" - the Fresh Open Source Software Archive

Member "gawk-5.1.0/README_d/README.development" (6 Feb 2020, 3503 Bytes) of package /linux/misc/gawk-5.1.0.tar.xz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 Wed Aug  7 20:58:29 IDT 2019
    2 ============================
    3 
    4 On Thu, Aug 01, 2019 at 11:57:11AM +0430, Saeed Dehqan wrote:
    5 >
    6 > How can I develop awk?
    7 >
    8 > For example adding a library or improving the speed and GAWK code.
    9 >
   10 > Can I add new features and send you a copy to check?
   11 
   12 "Andrew J. Schorr" <aschorr@telemetry-investments.com> wrote:
   13 
   14 > Hi,
   15 >
   16 > On Thu, Aug 01, 2019 at 11:57:11AM +0430, Saeed Dehqan wrote:
   17 > > How can I develop awk?
   18 >
   19 > Thanks for your interest.
   20 >
   21 > > For example adding a library or improving the speed and GAWK code.
   22 >
   23 > For adding extension libraries, please check out the gawkextlib project here:
   24 >    http://gawkextlib.sourceforge.net/
   25 >
   26 > The core gawk project is hosted here:
   27 >    https://savannah.gnu.org/projects/gawk/
   28 > You can check out the git tree like so:
   29 >    git clone https://git.savannah.gnu.org/git/gawk.git
   30 > and develop patches that you can submit to this list for review.
   31 >
   32 > > Can I add new features and send you a copy to check?
   33 >
   34 > There's a very high hurdle for adding new features to core gawk.
   35 > New extension libraries are definitely welcome.
   36 >
   37 > Regards,
   38 > Andy
   39 
   40 Arnold Robbins then expanded on this:
   41 
   42 
   43 | From: arnold@skeeve.com
   44 | Message-Id: <201908020824.x728OC7I024895@freefriends.org>
   45 | Date: Fri, 02 Aug 2019 02:24:12 -0600
   46 | To: saeeddhqan@gmail.com, aschorr@telemetry-investments.com
   47 | Subject: Re: [bug-gawk] develop gawk
   48 | Cc: bug-gawk@gnu.org
   49 | 
   50 | Hi Saeed.
   51 | 
   52 | Andy's answers are all correct, if a bit terse. :-)
   53 | 
   54 | Much more detail may found in the gawkworkflow.texi document in
   55 | the doc/ directory of the gawk distribution.  You should read that
   56 | document, as well as the section in the gawk manual on contributing
   57 | to gawk.
   58 | 
   59 | Here are the main points, in brief.
   60 | 
   61 | 1. Contributors are welcome, there's always stuff to do. I'm very glad
   62 | that you're interested in contributing!
   63 | 
   64 | 2. You need to be willing to sign paperwork assigning copyright in your
   65 | contributions to the Free Software Foundation.
   66 | 
   67 | 3. You should be comfortable using Unix/Linux command line tools and
   68 | programming in C. You should also be comfortable with Git, although the
   69 | above-mentioned document does provide a short primer on its use.
   70 | 
   71 | 4. As Andy mentioned, new extension libraries are (a) very welcome,
   72 | and (b) should go into the gawkextlib project, not the gawk distribution.
   73 | 
   74 | 5. There is essentially a moratorium on adding new features visible at
   75 | the language level to gawk.  (With one possible exception.)  If you have
   76 | ideas for new features, you'll have to work to convince me to add them. :-)
   77 | 
   78 | 6. However code improvements and performance improvements are very
   79 | welcome. There is one branch in particular that has been rather neglected
   80 | that may offer some nice improvements in memory usage and it'd be great
   81 | to have someone tackle it.
   82 | 
   83 | 7. If you start working on something, the way to submit changes is to
   84 | mail patches to this list.  I and the other gawk developers will review
   85 | your patches and either merge them as appropriate or give you feedback
   86 | about them. (Merging requires that you've signed paperwork.)
   87 | 
   88 | 8. Assuming that things work well, then eventually you'll be granted
   89 | write access to the Git repo.  There is still a review process, but
   90 | you'll be able to commit your changes yourself instead of my having to
   91 | do it.
   92 | 
   93 | In short, talk to me about what you'd like to work on (or what I'd like
   94 | you to work on, either way), clone the repo, and dive in!
   95 | 
   96 | Much thanks
   97 | 
   98 | Arnold