Thorsten Froehlich <nomail@nomail> wrote:
> The place where it is used is the core part of the tokenizer. Using a
> dynamically allocated string would significantly increase overhead in the most
> called place as the short string optimization won't work (it is frequently not
> more than 10/14 chars). Now consider the average POV token length, and you
> notice
> you get at least one additional memory allocation per token parsed.

Does the part that parses tokens really need to use the exact same string
class as the part that parses and handles strings?

> However, as you can concat strings to any length in POV, this is neither a bug
> now something that needs to be fixed. To the contrary...

Using concat to get longer string literals is a kludge.

-- 
                                                          - Warp

Post a reply to this message