Follow-up Comment #8, bug #66452 (group groff): At 2026-01-16T17:36:55-0500, G. Branden Robinson wrote: > Follow-up Comment #7, bug #66452 (group groff): > > At 2026-01-16T17:19:52-0500, G. Branden Robinson wrote: >>> Should we mention the speed improvement for very large fonts by >>> using Inline-C. >> >> Sure! I don't think I've actually even looked at the code for that, >> so I'll eyeball it and write something up. > > Ah! I did, it was simply over 2 years ago.
I think I'll forego an item on inline C; it's literally an
implementation detail, not a matter of user interface or raw capability.
Plus, you've arranged for _gropdf_ itself to warn the user if they're
trying to deal with a gigantic font without support for Perl's "Inline"
module, so anybody who needs to know about will be told. (The rest, if
they think about it at all, will merely unfairly credit Perl with
screaming performance. ;-) )
Thanks for illustrating that technique with `exec`; I knew (or once
knew) how to do an "attempted" module import in Python with
recovery/fallback, but never in Perl. I might need to use that
knowledge when I start whacking on glilypond. It desires an optional
CPAN module and fails in an ugly way if it's not present.
Regards,
Branden
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66452>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
