Re: Interest in new parsing library?

From: Joel de Guzman (djowel_at_[hidden])
Date: 2023-12-29 13:57:24

On 12/29/23 5:52 PM, Andrzej Krzemienski via Boost wrote:
> czw., 28 gru 2023 o 22:05 Zach Laine via Boost <boost_at_[hidden]>
> napisał(a):
>
>> I'm trying to gauge interest in a parsing library to replace
>> Boost.Spirit 2/Spirit X3.  I'm also looking for endorsements.
>>
>> The library is intended to remedy some shortcomings of Boost.Spirit*.
>> I think these are great libraries, but Spirit 2 was written in pre-11
>> C++ (I think; certainly its dependencies were).  Most-to-all of the
>> downsides stem from that -- long compile times, inscrutable
>> compilation failures, etc.  (Boost.Parser compile times are quite
>> low.)
>>
>> I'm calling my proposal Boost.Parser, and it follows many of the
>> conventions of Boost.Spirit  2 and X3, such as the operators used for
>> overloading, the names of many parsers and directives, etc.  It
>> requires C++17 or later.
>>
>> [snip]
>>
>>
>> [snip]
>>
>> What is the recommendation of Boost.Spirit authors to the programmers that
>> need to do parsing? Is Boost.Parser simply the newer and improved version,
>> or do they have disjoint sets of use cases?
>>
>> Personally, skimming through the docs, I find the feature of producing
>> custom error and warning messages very attractive. This is what I was
>> always missing from the parsing libraries.
>>
>> Thanks again for your effort.

Hello Y'all,

I support this endeavor. Zach already discussed this with Hartmut and I a year
or so ago. Unfortunately, I'm no longer able to dedicate time to supporting
Boost.Spirit after more than two decades. Nikita currently serves as the
maintainer and has been incredibly noteworthy, with the extent of his assistance.
But he does not seem to be active recently. So unless somone steps up to maintain
Boost.Spirit, perhaps it's time to retire the library :-(

Regards,
-- 
Joel