User forums > Nightly builds
The 12.11 RC2 (23 November 2012 build 8598) is out.
MortenMacFly:
--- Quote from: SC on November 24, 2012, 04:53:00 pm ---It is mixing directories of MSVC8 and MSVC9. One can correct if by referring to only one of the two versions in the include directies and Compiler's installation directory.
--- End quote ---
This is for convenience only, as if the compiler cannot be 100% detected, default path's are used. Its up to the user to verify the setup for the chosen compiler, so its not really a bug. You cannot rely 100% on the auto-detection engine as you can have thousands of editions and different ways to install these.
However, we plan a massive change to the compiler framework after the release which will address such issues easier-
Teybeo:
Problems with UTF-8 here too, quick feedback.
I open a project, open a file in it and in Edit -> File encoding the value is "System Default" whereas the file is UTF-8.
In 8549 aka RC1 and all others builds I used before, the value is correctly "UTF-8".
Futhermore, in this build, I manually select "UTF-8" for a file, save it, close and reopened it and the value is "System Default".
Maybe it's from me but i doubt...
MortenMacFly:
--- Quote from: Teybeo on November 24, 2012, 09:21:39 pm ---Problems with UTF-8 here too, quick feedback.
--- End quote ---
This is not a bug.
If you want to use UTF-8 and be safe, use a BOM (you can enable this in the editor settings). All other can hardly be detected as UTF-8 safely. The reason is, that if you use standard C/C++ code its always ANSI characters, no matter if you chose UTF-8 or not. Therefore, when loading it becomes "system default" - the encoding that was detected for ANSI.
So again: If you want to always use UTF-8, enable BOM. However - keep in mind, that there are compiler that will not understand such a file format. So don't blame us if it doesn't compile.
Instructions:
- open file
- menu "Edit" -> "File encoding " -> enable "Use BOM"
- menu "Edit" -> "File encoding " -> enable "UTF-8"
- save file
- load file -> will be UTF-8
Teybeo:
Well, I confess that I am really not a pro with these encoding questions, I guess I should have search more before posting here this quick :/
I don't really understood your explanation.
I choose UTF-8 because I thought it was the "universal" encoding solution and it will make things easier than with ISO-8859. I could use a BOM but I don't know if it won't bring new compatibility problems... I guess I should search and try.
The thing is I never had any problems with all my C files in UTF-8 until this release so I suspected it may be a change in it, not saying it's a bug.
And btw, I used special symbols only in comments so my code always compile :)
Sorry if I irritated you, if you think I'm beeing annoying, tell me and I will search by myself :)
MortenMacFly:
--- Quote from: Teybeo on November 25, 2012, 01:50:06 pm ---Sorry if I irritated you, if you think I'm beeing annoying, tell me and I will search by myself :)
--- End quote ---
Don't worry - what would be more helpful is to provide a sample that worked before and behaves different now.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version