The 13 august 2007 build (4368) is out.

[killerbot]

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx284.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10.7z

The 13 August 2007 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20070813_rev4368_win32.7z
  - Linux :
   http://prdownload.berlios.de/codeblocks/CB_20070813_rev4368_Ubuntu6.10+7.04_wx2.8.4.tar.gz
   http://prdownload.berlios.de/codeblocks/CB_20070813_rev4368_Debian4.0_wx2.8.4.tar.gz (not yet)
   http://prdownload.berlios.de/codeblocks/CB_20070813_rev4368_suse100-102.wx28.i586.rpm (not yet)
   http://prdownload.berlios.de/codeblocks/CB_20070813_rev4368_fc4+5.i586.rpm (not yet)


Resolved Fixed:

• KeyBinder 1.0.42 2007/08/12 : Change AddPendingEvent() to ProcessEvent() in wxMenuCmd::Exec() to avoid crashes when secondary command key would close editors wx284
• Fixed: C::B can't detect a file with UTF-32LE (with BOM) encoding

Regressions/Confirmed/Annoying/Common bugs:

• toolbar-images-not-changing-state (is a wx problem/Win XP problem)

[Xaviou]

Ubuntu 6.10 & 7.04 Amd64 tar.gz archive (containing '.deb' installers builds with wx284) can be found here.

[pasgui]

Build for Ubuntu 7.04 i386 can be found here

[san]

Build for Ubuntu 7.04 i386 can be found here

Thanks for you repository.. it makes updating even more smooth

only the download is a bit slow

[Steven 'lazalong']

Could it be possible to have the highlighting for the "Preprocessor" dependent on its scope?

For example on a Win32 platform

   #ifdef PLATFORM==WIN32
      #define THAT
   #else
      #define THIS
   #endif

On linux, macos, etc. you would have :

   #ifdef PLATFORM==WIN32
      #define THAT
   #else
      #define THIS
   #endif

Of course, the #defines in the project build options should also be taken into account.

I didn't see this as a feature request... but perhaps I didn't check it correctly.

[killerbot]

file it as a feature request. M$ has this but they have it because they use the compiler for code completion, and as such they know which ones are active. Rather difficult !

[Steven 'lazalong']

file it as a feature request. M$ has this but they have it because they use the compiler for code completion, and as such they know which ones are active. Rather difficult !

Ok - done  http://developer.berlios.de/feature/?func=detailfeature&feature_id=3645&group_id=5358

[thomas]

Don't be disappointed if this takes a long time to be implemented, or if it is never implemented, though.

It would take considerable work to be implemented, and it would take considerable CPU time at runtime, too. It is easier for Microsoft to do that, because they only support one compiler architecture which has been designed for that purpose, too.

For us, it means that we would have to keep two copies of the text, filter it through the preprocessor (which requires executing an external process), and do a binary comparison of the two to figure out the differences (which is tough).
Or, we would have to create a pseudo-sourcefile on the fly that contains all preprocessor commands of the original and that conditionally enables/disables marker textblocks via the preprocessor (again, by launching an external process).
This would have to be done after every edit, unless we add a parser that detects whether a preprocessor directive was changed, too.

[raph]

Giving codecompletion an basic c preprocessor would improve its quality (e.g. WinAPI functions could be parsed then).
Cc could give scintillas syntax highlighting some hints (e.g. give a variable an unique color etc).

[byo]

Giving codecompletion an basic c preprocessor would improve its quality (e.g. WinAPI functions could be parsed then).
Cc could give scintillas syntax highlighting some hints (e.g. give a variable an unique color etc).

AFAIK CC have basic preprocessor, the problem is that wxScintilla doesn't allow generating really custom lexers - you choose one of predefined which can be used for given language and customize it (add special identifiers etc).
To add extra colourising (like changing colour of identifiers) we would have to make big code changes into wxScintilla code. That would be really great because of all the features it would introduce, but it may be some harder task.

Regards
   BYO

[foomaster]

why not work with a file that is in memory? then use a simple parser and a manager to track each of the defined macros and their values. after that the manger can easily determine which symbols and parts of the file to keep in memory and pass them to the code completion plug-in? this way the program would use less memory for small projects and more for really large ones and actual files would be used when the users saves them. for larger projects a manager to keep track of the active project parts would greatly reduce the memory which is used. the latter could be implemented by keeping a dependency tree for each file and freeing the memory for the unused files. this manager, of course, would be active only when a given number of symbols is defined or a given total number of lines is reached, or a given amount of memory for parsing is used. this is just an idea and requires a lot of work, but certainly is not impossible.

ps and a code completion cache would be necessary in this case, but you are probably using one, so it would need only slight modifications.

[Steven 'lazalong']

This would have to be done after every edit, unless we add a parser that detects whether a preprocessor directive was changed, too.

If it is very cpu expensive it could be implemented as an add-on that you call on-demand.
I don't change my #defines and compiler options all the time so I don't need it to be highlighted all the time. I need it when I come across a new library containing extensive preprocessor code in its .h

If M$ uses his compiler to do it perhaps you can use the available compiler by this on-demand feature.
(Just a wild idea: no idea how to implement it.)

No problem if this takes a long time to implement