The 27 November 2010 build (6863) is out.

[oBFusCATed]

The problem with this method is that it breaks this rule: http://www.faqs.org/docs/artu/ch11s01.html
That is why I've said 'the API is broken'.

[AndyJ]

For the last few nightly releases I've found that starting CB and dragging a workspace file onto it seems to result in CB hanging most of the time. I then have to manually kill it. This is on Win XP. Has anyone else experienced this, or is it something specific to my computer?

Thanks for the great work.

[MortenMacFly]

The problem with this method is that it breaks this rule: http://www.faqs.org/docs/artu/ch11s01.html
That is why I've said 'the API is broken'.

You have a const literally for everything. I've learned the meaning of const once (during studies) as the following:

 const int* const my_method(const int* const&) const;
 - the var pointed to by the returned ptr  won't be changable
 - the returned ptr itself                 won't be changable
 - the var pointed to by the given ptr     won't be changable (by the method)
 - the given ptr itself                    won't be changable (by the method)
 - the object the method belongs to        won't be changed (during method call)

According to this the const only tells you "wxArrayString does not modify it's internal members when you use the operator method []". This is true, even in out case. If we modify the reference we get that this has nothing to do with it anymore, as the call to the operator is done, so the validity of the const rule.

Anyway - it's getting quite philosophic. I think the good thing is simply that you found that bug. Let the wx guys decide if/how to react. Having the knowledge in mind we know now what we shouldn't do next time... ;-)

[oBFusCATed]

Let the wx guys decide if/how to react.

They would do nothing, they like it the way it is now :x :twisted:

[cacb]

OK, I have the steps to reproduce:

1. Close C::B if it is open
2. Double click on a project in explorer/total commander
3. Open a .cpp file and type #include "|<- press ctrl + space
4. Open the build options and you have your global vars broken....

Great!! Sounds like you have found it. This has been one of my biggest issues with C::B lately, it has caused me a lot of frustration. If this is now solved, I am really happy 

So which is the first nightly with this bug fixed? I am going to install that ASAP!

[oBFusCATed]

The next one

[cacb]

The next one

Ok, as this bug was rather annoying for several people, I hope that means "very soon"  :lol:

[Folco]

If the patch has been commited, you could compile CB to get this bug out ?

[Jenna]

If the patch has been commited, you could compile CB to get this bug out ?

Should work.
If you use my repo (debian): I just finished compiling the latest trunk.