bug-gperf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[sr #110791] Patch from Sei Lisa


From: Frediano Ziglio
Subject: [sr #110791] Patch from Sei Lisa
Date: Tue, 29 Nov 2022 11:01:51 -0500 (EST)

URL:
  <https://savannah.gnu.org/support/?110791>

                 Summary: Patch from Sei Lisa
                 Project: gperf
               Submitter: freddyz77
               Submitted: Tue 29 Nov 2022 04:01:49 PM UTC
                Category: None
                Priority: 5 - Normal
                Severity: 3 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
        Operating System: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Tue 29 Nov 2022 04:01:49 PM UTC By: Frediano Ziglio <freddyz77>
In some internal project I'm trying to use GNU gperf to generate code for
Golang. After a quick attempt to change code generation code in output.cc I
found a fork from Sei Lisa at https://github.com/Sei-Lisa/gperf-hfn,
specifically the commit at
https://github.com/Sei-Lisa/gperf-hfn/commit/5069a9ece3662e1dd652b9845c7fffc207dd0b5e.

I saw the change was discussed at
https://lists.gnu.org/archive/html/bug-gperf/2016-11/msg00000.html.

Personally I think that the change is pretty useful and should be integrated.
That allows to use GNU gperf for languages not supported. Why not integrating
other languages instead? One of the reason is that it could clutter GNU gperf
sources with languages used rarely. Another is that there could be generators
written in other languages which are easier to use.

Personally I think that program could be also split into lookup generation and
code generation. This way you can generate code again from the same set of
strings without having to go through the slow lookup generation.







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?110791>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]