Dusan Popovic wrote:

> I am doing some work on gvim that will hopefully result in further
> optimization in rendering and proper usage of ligatures. Since I just
> opened vim code last night, there is number of building blocks I have to
> find. Maybe they already exist in gvim, maybe we need to fall back to
> Pango or some other solution... I don't know yet. Please take a look
> below and tell me what building blocks we already have.

I haven't looked at this code recently, and I didn't write it (perhaps
some fixes over time), but I thought the idea was that a lot of text is
ASCII and we wanted to make sure that can be drawn quickly.  Any
non-ASCII might require special handling (especially composing
characters).

If you now also use the special handling for some ASCII characters,
perhaps the special casing can just be skipped?  So instead of
specifying exactly what ASCII characters should be given the special
handling, just make an on/off switch.  What would the performance impact
be?  Perhaps if letters and digits can still be handled like ASCII now
the speedup is noticeable.

General rule: don't optimize code for speed unless you can measure the
improvement.

-- 
hundred-and-one symptoms of being an internet addict:
75. You start wondering whether you could actually upgrade your brain
    with a Pentium Pro microprocessor 80.  The upgrade works just fine.

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \\\
///                                                                      \\\
\\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20210928213545.AA600C80054%40pakwach.

Raspunde prin e-mail lui