Send MinGW-Notify mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.osdn.me/mailman/listinfo/mingw-notify
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of MinGW-Notify digest..."


Please do not reply to this notification; the sender address is unable to 
accept incoming e-mail.  If you wish to unsubscribe you can do so at 
https://lists.osdn.me/mailman/listinfo/mingw-notify.



Today's Topics:

   1. [mingw] #39246: Please update MSYS awk; current awk-3.1.7
      implementation is too old to remainviable (MinGW Notification List)


----------------------------------------------------------------------

Message: 1
Date: Fri, 03 Jan 2020 16:28:18 -0300
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #39246: Please update MSYS awk;
        current awk-3.1.7 implementation is too old to remainviable
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8

#39246: Please update MSYS awk; current awk-3.1.7 implementation is too old to 
remain
viable

  Open Date: 2019-05-16 19:44
Last Update: 2020-01-03 16:28

URL for this Ticket:
    https://osdn.net//projects/mingw/ticket/39246
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=39246

---------------------------------------------------------------------

Last Changes/Comment on this Ticket:
2020-01-03 16:28 Updated by: cstrauss

Comment:

Dear Keith,

I will package GNU awk 4.0.1, which seems to build and run fine on current
MSYS, despite some failures in the test suite.

I'm interested in switching to your mingw-pkg tool. Is it already usable? I
went as far as creating a recipe, but got stuck on the distribute step.

Regards,

Cesar



---------------------------------------------------------------------
Ticket Status:

      Reporter: keith
         Owner: cstrauss
          Type: Feature Request
        Status: Open [Owner assigned]
      Priority: 5 - Medium
     MileStone: (None)
     Component: MSYS
      Severity: 5 - Medium
    Resolution: None
---------------------------------------------------------------------

Ticket details:

While developing this Mercurial Queues emulation for Git, which will be
required to support git integration for this proposed MinGW package builder
tool, I've run into a problem with the MSYS implementation of awk. On my LMDE
system, I have awk-4.0.1, and I've written an emulator for "git qselect
--series", (which I've yet to publish to the git-mq chamber). This used gawk's
"asorti()" function, with a custom sort-comparator function, to present the
output in lexically sorted order; it works fine in awk-4.0.1, but fails on
MSYS, which offers only awk-3.1.7; (the "asorti()" function appears to be
supported, but the custom comparator function reference parameter is rejected).

I've since reworked my "git qselect --series" emulation, using my own "qsort()"
function implementation, instead of gawk's "asorti()" function. This makes the
entire emulation significantly more portable, but it may still make sense to
upgrade the MSYS implementation of awk, such that it will support more modern
gawk features.



-- 
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN

Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net

URL for this Ticket:
    https://osdn.net/projects/mingw/ticket/39246
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=39246


------------------------------

Subject: Digest Footer

_______________________________________________
MinGW-Notify mailing list
[email protected]
https://lists.osdn.me/mailman/listinfo/mingw-notify


------------------------------

End of MinGW-Notify Digest, Vol 28, Issue 1
*******************************************

Reply via email to