From: Hugo Rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Gawk in 9front-ports
Date: Thu, 9 Jul 2015 08:33:49 -0400 [thread overview]
Message-ID: <CAFo14L2usuu90njUZCV5McuwGdF0zXABO-s1YHg8iTAbMcWqNw@mail.gmail.com> (raw)
In-Reply-To: <201507090849.t698nrAx021303@freefriends.org>
Arnold,
I am not sure who I am addressing either :-) Just wanted to know where
this gawk port was heading.
The thing is that I use a slightly modified version of Plan 9's awk.
In this version, I added all the math functions from C and replaced
the random number generator by the Mersenne twister.
As a comment, from my experience gawk is generally faster than Plan
9's awk, but I believe the latter is more reliable (it crashes less
often than gawk).
Please, let me (us) know about the future of awk in 9front.
2015-07-09 4:49 GMT-04:00 <arnold@skeeve.com>:
> Hi Hugo. I'm not sure who you're addressing. Jens did the port.
> I maintain gawk.
>
> Removing bloat unfortunately isn't going to happen in the mainline
> code base since there are backward compatibility issues.
>
> However, I'm happy to incorporate portability changes to make porting
> to Plan 9 easier, if they're reasonable.
>
> HTH,
>
> Arnold
>
> Hugo Rivera <uair00@gmail.com> wrote:
>
>> Let me understand. Are you going to modify the current gawk version
>> according to your needs (perhaps removing some of the bloat you
>> mention)? or are you going to port gawk as it is?
>>
>> 2015-07-08 2:22 GMT-04:00 <arnold@skeeve.com>:
>> > Hugo Rivera <uair00@gmail.com> wrote:
>> >
>> >> Why do you want gawk on plan9?
>> >
>> > I appreciate knowing about portability issues. :-)
>> >
>> >> I use awk a lot (on plan9 and elsewhere) and I wonder what reasons do
>> >> you have to use gawk over plan9's awk.
>> >
>> > Many features and extensions over standard awk. Different people will
>> > assign different levels of value to said features and extensions.
>> > A partial list:
>> >
>> > - The previously discussed dynamic plug-in facility
>> > - And awk-level debugger
>> > - A statement count profiler (and a pretty printer)
>> > - True arrays of arrays
>> > - Many more built-in functions and variables. In retrospect, some of these
>> > are just bloat and I'd have been better off without them.
>> >
>> > Arnold
>> >
>>
>>
>>
>> --
>> Hugo
>
--
Hugo
prev parent reply other threads:[~2015-07-09 12:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 2:37 Jens Staal
2015-07-07 12:27 ` arnold
2015-07-07 15:25 ` Jens Staal
2015-07-07 15:45 ` Charles Forsyth
2015-07-08 12:48 ` Jens Staal
2015-07-07 21:56 ` erik quanstrom
2015-07-07 22:36 ` Kurt H Maier
2015-07-08 1:47 ` Hugo Rivera
2015-07-08 6:22 ` arnold
2015-07-08 20:05 ` Hugo Rivera
2015-07-09 8:49 ` arnold
2015-07-09 9:58 ` Jens Staal
2015-07-09 10:19 ` Steve Simon
2015-07-09 12:31 ` Jeff Sickel
2015-07-09 13:50 ` erik quanstrom
2015-07-09 15:24 ` [9fans] origins of configure arnold
2015-07-09 15:45 ` tlaronde
2015-07-09 18:11 ` arnold
2015-07-09 12:57 ` [9fans] Gawk in 9front-ports Jens Staal
2015-07-09 12:33 ` Hugo Rivera [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFo14L2usuu90njUZCV5McuwGdF0zXABO-s1YHg8iTAbMcWqNw@mail.gmail.com \
--to=uair00@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).