Comment Re:BOOST::Python, but you haven't seen the source? (Score 1) 658
Hello again
I've finally gotten around to compiling your example with MSVC. A complete compile link cycle takes 10 seconds on my 3.2GHz Pentium 4, with a very small bump (50MB) in the memory graph (my box has 1GB).
Regarding the large binary sizes you reported by private email:
With MSVC the executable is 200KB, but I do remember that I sometimes had very large binaries with mingw. I guess this is somehow connected with the compiler/linker taking so long. Might be worth reporting to the gcc developers. Unfortunately, I don't have much time to spend on statechart at the moment as my job is currently very demanding and I'm also in the process of moving to new hardware. So I'm afraid I won't be able to look into this more deeply in the next few weeks.
Andreas
I've finally gotten around to compiling your example with MSVC. A complete compile link cycle takes 10 seconds on my 3.2GHz Pentium 4, with a very small bump (50MB) in the memory graph (my box has 1GB).
Regarding the large binary sizes you reported by private email:
With MSVC the executable is 200KB, but I do remember that I sometimes had very large binaries with mingw. I guess this is somehow connected with the compiler/linker taking so long. Might be worth reporting to the gcc developers. Unfortunately, I don't have much time to spend on statechart at the moment as my job is currently very demanding and I'm also in the process of moving to new hardware. So I'm afraid I won't be able to look into this more deeply in the next few weeks.
Andreas
