On Fri, 2010-01-08 at 17:05 +0200, Aurimas Juška wrote:
> Hi,
> On Fri, Jan 8, 2010 at 4:30 PM, Martin Nordholts <ense...@gmail.com>
> wrote:
>         We need to be aware of that we are introducing extra disk IO
>         which can give us problems, especialy during startup if we
>         have to load a lot of files. In practice I don't think this
>         will be a problem for a long time though, but doesn't hurt to
>         have a mitigation strategy. We could:
>         * Put files as static strings in the code so that we don't
>         have to
>         significant disk IO at all
>         * Merge several files together to minimize disk seeking times
>         for many files
> Why not to convert XML's to C code when compiling distribution ? XML's
> are large and not very fast to parse. This approach would have all the
> benefits of XML's while developing and would not cause additional
> penalties for release distribution. 

Can you back up your claims that parsing the XML would have noticeable
impact? I am pretty sure that the effect is negligible. So
pre-processing the XML to C code would make things more complex without
any need and it has the potential danger that people start to edit the
generated code. The solutions that Martin suggested can be considered
when it turns out that parsing the XML becomes a problem. Converting to
code is certainly not an option we should consider.


Gimp-developer mailing list

Reply via email to