- Q: Which version of
VC++ is targeted?
- A:
C++/CLI (2005 and above) code is produced.
- Q: Are entire
folders converted?
- A:
You can select Java folders to convert. All ".java" files
within that folder will be converted and written as
either combined declaration/implementation header files or as
traditionally separated .h/.cpp files to the
directory you specify. However, Instant C++ does not
construct the new VC++ project file. This is due to the
lack of one-to-one correspondence between Java project types and
formats and VC++ project types and formats.
-
- Q: Is the original
Java code
altered in any way?
- A:
Your existing code is left completely intact. The new
C++
files are written to the new
location that you specify.
- Q: Do you guarantee
a 100% complete conversion?
- A:
No. Our converter accuracy is the highest in the industry, but
there will be some minor tweaks required in all but the most
trivial conversions. Read the rest of the FAQ to get an idea of a
few things that are not converted. It
is critical to try some of your own code when comparing Java to
C++ converters since it is very easy to create a converter
that does very well on a
specific sample set. The most important criterion is how
well the converter does on your own code, and this is where
Instant C++ (Java Edition)
will clearly show its superiority.
-
- Q: What are the most
common manual adjustments?
- A:
-
●
Types must be declared before they are used
in C++. Instant C++ does not move type declarations around
to satisfy this C++ requirement. In Java there is no such
requirement since the Java compiler makes more than one pass
through the source code.
-
-
●
Same class constructor calls are not
supported in C++. These cases are marked with "ToDo"
comments.
-
-
●
Most Java platform or library method calls
are left unconverted. Instant C++ converts a few that have
direct equivalents, but most will remain in the converted code
and will require refactoring.
-
-
●
You cannot initialize non-static class fields
in their declarations
in C++, so these are marked with "ToDo" comments. The
recommended solution is to move the initializations to a
constructor or common method called by all the existing
constructors.
-
●
Java's workaround for event handling has no
direct equivalent in .NET's simple and concise event handling
model.
●
Java wildcard generics have no equivalent in
C++/CLI, unless used in a method declaration parameter list.
●
Java local classes or anonymous classes
cannot be declared within methods in C++/CLI. These are marked
with a comment.
●
There will be occasional qualifier symbol
adjustments required. For example, it is possible that
Instant C++ fails to determine whether a particular Java dot
operator should be replaced by a C++ arrow, double colon, or
dot. If type analysis fails to determine the equivalent,
heuristics are used to determine the most probable equivalent.
-
●
Since Instant C++ does not map to a
particular C++ project type, the Java 'main' method is left in
it's original location and converted literally. Depending
on the C++ project type, you will need to adjust the location
and structure of the main method.
|
