Wt

Forgot to sign in when creating this issue.

Wim Dumon wrote:

Hi Mark,

That's weird. Is it consistently reproducible? What is your testcase? Does it also occur with one of the Wt examples?

BR,

Wim.

Yes it is consistent and it does seem to occur in the 'planner' example, although in the example it appears as a browser popup with the error message "Wt internal error: SyntaxError: Unexpected token :, code: undefined, description: undefined" when you click in one of the calendar squares.

Wim Dumon wrote:

Cannot reproduce with (patched) 1.54 with msvs 2012. I verified that chrome does indeed receive the correct contents. I will try with boost 1.55 (compiling now).

Did you do a clean rebuild (remove build directory & restart from scratch) to exclude a build error of some kind?

Wim.

Yes this was with done with clean builds using Visual Studio '2013' and Boost 1.55.0.

Mark,

Something goes wrong with reading the minified file. Must be related to MSVS2013. I will take a look at this.

BR,

Wim.

My minimal test case:

#include <iostream>

#define A(i, j) const char *str##i = #j;

A(1, L?)
A(2, S?)

int main()
{
    std::cout << str1 << std::endl;
    std::cout << str2 << std::endl;
}

MSVS 2010 says:

L?
S?

MSVS 2013 says:

L
S?

Anyone? :)

BR,

Wim.

This appears to be a problem with the 'L' character. L is used by the compiler before a string to identify it as unicode, e.g. L"abc". It seems to confuse the preprocessor in this case.

A fix is to not use 'L' here, or put a space between the L and ?

Mark Snelling wrote:

This appears to be a problem with the 'L' character. L is used by the compiler before a string to identify it as unicode, e.g. L"abc". It seems to confuse the preprocessor in this case.

A fix is to not use 'L' here, or put a space between the L and ?

I have filed a bug report with Microsoft here https://connect.microsoft.com/VisualStudio/feedback/details/813595/c-preprocessor-incorrectly-handling-l-character

Koen Deforche wrote:

I have a workaround for this using the ---externs command line option of the minifier.

Thanks, MS have fixed the compiler bug and it should be in the next major VS release. Do you have a patch that I can apply to my source until 3.3.2 is released?

Hi Mark,

The quickfix: just put back the ? that MSVS deleted. It's the only instance that we know of that had a problem. In the future, we will avoid L and R in minified JS.

Wim.

Wim Dumon wrote:

Hi Mark,

The quickfix: just put back the ? that MSVS deleted. It's the only instance that we know of that had a problem. In the future, we will avoid L and R in minified JS.

Wim.

Thanks but do you have an already minified .js file I can use that doesn't use the L character? Otherwise I would have to edit the .JS file as it's #include'd into the .cpp, and to be honest I don't know what I'm doing with JavaScript.