Re: [bug-gawk] FPAT bug?

[arnold]

As long as I am the maintainer, CSV parsing will not be built-in.
Libraries / extensions are the right way(s) to do that.

I will get around to investigating the issue with FPAT.

Arnold

Ed Morton <address@hidden> wrote:

> Andy - I THINK I have used FPAT for other things but I really don't remember 
> and 
> I can always write a while(match()) loop instead. So if gawk had a proper CSV 
> parser built in then I probably wouldn't need FPAT but if it's a library that 
> I 
> might need to download and compile then I wouldn't use that library as I've 
> no 
> time/patience for dealing with that if/when I'm just jumping onto someone's 
> computer to help them get a specific job done plus I often don't have 
> permission 
> to install anything myself on the machines I use so then I'd still need FPAT.
>
> Obviously what I suggested is just a temp workaround for us to get by until a 
> fix is available, not a solution.
>
>      Ed.
>
> On 4/2/2017 8:55 AM, Andrew J. Schorr wrote:
> > On Sat, Apr 01, 2017 at 04:27:46PM -0500, Ed Morton wrote:
> >> Might be useful until a fix is available. Any better ideas for now?
> > I have no better ideas, although I can't imagine that such a solution would
> > please anyone. Here's a crazy question: do you ever use FPAT for anything 
> > other
> > than CSV parsing? If gawk had a proper CSV parser library, would we need 
> > FPAT
> > at all? I don't think I have ever used FPAT (my personal CSV parsing library
> > takes a brute force string scanning approach), and it seems from the 
> > observed
> > bugginess that FPAT is not often used...
> >
> > Regards,
> > Andy
> >
>