Home » Community » U++ community news and announcements » uppconfig.h and SVO Value now default (and how to switch it off)
| uppconfig.h and SVO Value now default (and how to switch it off) [message #36010] |
Thu, 19 April 2012 09:02  |
 |
mirek
Messages: 13975
Registered: November 2005
|
Ultimate Member |
|
|
In the spirit of gradual move to new Value implementation, I have decided that we need new way how to configure U++ on per-assembly basis.
Core/config.h now includes
#include <uppconfig.h>
which is defined in uppsrc root. It now contains a single line
#define SVO_VALUE
to activate new Value implementation. However, if you feel like your application is too mission critical, it is possible to place another emtpy uppconfig.h without this define into your first nest (where you put packages of your application, "MyApps" in default installation) and new Value will not be active. (You can still switch it on by putting SVO_VALUE to main config).
Personally, I am keeping old Value active only for one missiong critical backend code. Perhaps I am just too prudent, I am running SVO Value ide since January without problems... and I guess it is in fact more robust than "OldValue", but I got scared by subtle late error found a month ago in SVO Value...
Mirek
[Updated on: Thu, 19 April 2012 09:03] Report message to a moderator |
|
|
|
|
|
Goto Forum:
Current Time: Mon Apr 29 10:29:46 CEST 2024
Total time taken to generate the page: 0.03023 seconds
|
Members
Pages
Help
Register
Login
Home
