No, I don't think so. My reply wasn't very well-worded. My point was simply
that differences can exist between versions, whether between releases (as
in the compiler and breaking changes) or between different SKUs of the same
release. It was an example, not specifically addressing the Pro/Express
issue.
That said, the Express edition does have limitations relative to the
Professional version (and any other retail version for that matter). I
would not expect to see actual compiler behavior differences (as it's using
the same compiler executable), but there could easily be differences in the
provided libraries or toolset that lead to different behaviors at
compile-time, even though the compiler is the same.
Assuming Tony is in fact not hallucinating, then there are pretty much two
possibilities:
-- The compiler is working exactly the same for both editions, but
receiving different inputs because of the Express/Pro difference, where the
inputs cannot compile in Express, but the _different_ inputs can compile in
Pro.
-- There's some other problem that has nothing to do with Express vs Pro,
where Tony has simply introduced a build break in his project when
transitioning between one version and the other.
As usual, without a concise-but-complete code example that reliably
reproduces the problem, along with specific descriptions of the exact error
message(s) being received, there's really nothing anyone else can do to
help. Clearly the behavior isn't impossible, because Tony has seen the
behavior.
Asking whether it's possible makes no sense whatsoever. What Tony ought to
be doing is posing a question that does make sense, along with sufficient
information for people to understand the question and offer advice and/or
answers.
