> The Wt crash when missing the config file happened just after the stat
> call, it started to create the parser for the file, but never
> initialized the memory for it, and ended up crashing when it tried to
> read an std::string.  I fixed that rather quickly (and recompiled Wt
> to point to some place other then a C: drive as a default location, I
> do not have a C: drive, my boot drive is G: and my windows install is
> on F:, don't ask, this computer is an evolution of 15 years of
> upgrades...).  It might have been due to more of the drive missing
> rather then the file, I am not sure how stat handles that (I am not
> sure why stat is being used, why not just open the file without
> creation and see if you get a valid handle back, it is supposed to be
> more optimized to do it that way as well).
>

I tried to reproduce your crash but could not. Deleted all my config
files, looked in the source, but could not immediately find what
you're describing. I'm interested to see your patch, though. I also
looked at all calls we make to stat, and found only one that we make
on Windows - it mainly verifies if the type of the path
(file/directory/...) is as intended.

> I did notice some places where Spirit.Classic is used.  If you
> upgraded it to Spirit2.1 (or 2.2 in trunk) you would be a rather
> significant speed boost in execution speed for that code (Spirit2.x
> outperform Spirit.Classic by *far*, and it is a lot easier to use as
> well).  If you wish I could bcp out the Spirit2 code so it is
> self-contained (I could actually do that to all the used boost
> libraries if you wish, then you would not need boost as a requirement,
> although everyone should have it anyway in my opinion) in case they do
> not have 1.41.  I could easily make the conversion if you are curious,
> I know Spirit *very* well.
>

Looking forward to your contribution... When did Spirit2 make its
intro? Currently we depend on boost >= 1.35, and I'm wondering if we
should support Spirit.Classic for backward compatibility reasons.
There's no need to put parts of boost in Wt.

Regards,
Wim.

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to