When you invoke a method with a variable argument list (also called varargs ) you will occasionally find that the compiler issues an unchecked warning. Here is an example: warning: [unchecked] unchecked generic array creation of type Pair<String,String>[] for varargs parameter The first invocation is fine, but the second invocation is flagged with an unchecked warning. This warning is confusing because there is no array creation expression anywhere in the source code.

Ask the user to open a new shell. The best way to do this is system("echo Please open a new shell now."); sprintf(cmdstring, "echo Enter the command '%s' in it.", cmd); system(cmdstring); The traditional solution, pioneered by Microsoft, is to sell enough copies of your proprietary, slow, and limited software that everyone else supports your formats.

Unfortunately we are not staffed to provide answers to these types of questions. Many of these questions are answered in The Java Tutorial. You can also try the Java Technologies for Web Services at the JDC. By the way, we tested all of the examples in the book on Suns, and PCs. The examples work for us. If you are having problems with the examples, then you are probably having configuration problems. We get a fair number of messages to our e-mail address, users@jwsdp.dev.java.

Apparently, yes! Thanks to Tilo Winkler for providing an example of spawning DenyHosts from TCPWRAPPERS.

Well, firstly we are developing a Windows user interface. This will be Win-32, i.e. it will run under Windows 95 and Windows NT. But since the compiler is a non-graphical application, and the DOS interface runs quite happily under all flavours of Windows already, it has not been as high a priority as making sure that the basic functionality is top-notch. In other words, we believe an excellent compiler with a DOS front-end is better than an average compiler with a Windows front end.

The compiler is slow at compiling my program, why? A: When you install the compiler it will operate in demo mode for 21 days. When the compiler is in demo mode some compiler options are disabled and there is a delay compiling files. To active the compiler you must register it. You can register on-line from the HI-TECH web site. Go to: http://www.htsoft.com/support/register.php If you have any problems registering or require more information about registration, please contact sales@htsoft.

To install two or more versions of the same compiler you will need to follow the following procedure: Install the first compiler as normal. Make note the of the directory where the compiler was installed for the PICC compiler it will be, by default, 'c:\ht-pic'. Then before you install the second compiler rename the installation directory, for example 'c:\ht-pic' maybe renamed to 'c:\ht-pic_7_86pl4'.

For a while, Unix distributions included both an interpreter and a compiler; but the interpreter is is usually fast enough even for production work, and most people found that using the compiler wasn't worth the extra compilation time or the hassles involved. We no longer advertise the compiler or produce binaries for it. It is still part of the source code distribution, and we have not deliberately broken it, but we no longer support it and we cannot offer help if problems arise.

Software is compiled in traditional programming in order to optimize human readable code for machine reading, making the computing process more efficient, reducing duplication and redundancy. Until the w3compiler, this concept has not been applied to Web site and application code. We strongly believe that the code Web developers write for themselves should not be the same code that is delivered to end users.

Look in PhysioToolkit, the repository for all software available on this site. With very few exceptions, the software available here is portable among all popular operating systems, including GNU/Linux, Mac OS X, MS-Windows, and Unix. Since all of it is provided in source form, you can compile it (using free or proprietary compilers) into binaries that can run under any of these operating systems.

When you run the Inform compiler, you have as a minimum to tell it the name of the source file containing your game. For example, assuming that Inform represents the compiler program, and that your current folder/directory contains an error-free source file myGame.inf as well as all of the library files, then on a PC this command should be sufficient to create a Z-Machine game myGame.z5: Inform myGame Often, you need to provide additional information to the compiler.

The AspectJ compiler or weaver is required at some point, but many people can use AspectJ without changing their build or deployment process significantly. For aspects that are not required to compile, you can use the AspectJ binary weaver, run at build-time or class-load-time. You can write aspects using the original code style (which must be compiled with the AspectJ compiler) or using the annotation style new in AspectJ 5 (which may be compiled with Javac or the AspectJ compiler).

How do I use scanf() and gets() functions with the PICC/PICC-18 compiler? A. The gets() function is not supplied by the compiler. Becuase gets() will get a string from a programer specified input, such as the serial port, it is easier for the programer to write this function then for it to be supplied in a library. There is a console get string function, cgets(), that will read string from an input using console formatting. The cgets() function is available in the cgets.

My compiler is running in demo mode. How do I activate it? A: To activate your compiler you must first register your details with HI-TECH Software. You can register o-line from the HI-TECH web site. Go to: http://www.htsoft.com/support/register.php After you have registered you will receive an activation key, and you will be directed to where you can download the full version of the compiler that can be activated. NOTE: The demo version of the compiler can no longer be acivated.

My program is larger after upgrading to a newer version of the compiler. Why? A: When a new version of the compiler is released, all reported bugs from the previous version are fixed. Sometimes when a bug is fixed the resulting code can be slightly larger. If you find your program is slightly larger after upgrading, then it could be that your code would have been effected by the bug when compiled with the previous version.

Migrating a project from the PICC to PICC18 compiler is not difficult. Here are the key points to observe: 1) SFR definitions - Your PICC project may include the file pic.h, just change this to pic18.h to get correct SFR definitions for your new target device. Note that the names of some SFRs may change when migrating across the archictures. You can consult the headerfile specific to your new target device if your old SFR names aren't recognised.

The compiler generated a very large COF file, why? A: Even though the file is large, it is valid and will work correctly. We have seen this happen with use of the CONFIG macro on the PICC-18 compiler. If you move the CONFIG macro to the top of the C file, this will fix the problem. Always be sure to install the latest updates for the compiler as these may fix the problem.