Jump to content
Excelsior Forums


Excelsior Staff
  • Content count

  • Joined

  • Last visited

Everything posted by snowman

  1. No, there are not. And please, please stop pushing us.
  2. snowman

    One more License Question

    An executable compiled by Excelsior JET 3.7 needs the Sun JRE to run if any of the following is true: 1. It uses J2SE 5.0 features. 2. It uses AWT or Swing. Note that there is an AWT bridge in SWT ([tt]org.eclipse.swt.internal.awt[/tt]), which you must explicitly exclude from the compilation set as described in this Knowledge Base article. 3. It uses the JDBC-ODBC bridge (AFAIK it is only required to access MS Access databases). 4. It uses the JPEG image manupulation classes. So if you use SWT for GUI and compile your app against a J2SE 1.3 or 1.4 based profile, it most likely won't need the JRE. To your other question, we plan to release Excelsior JET 4.0 in September-October 2005. It will create executables that will run without the Sun JRE regardless of what APIs they use, but they will have to be distributed with all JET runtime DLLs (in the current and previous versions you can omit the runtime DLLs that you think are not required.) So if download size in important for you, you may be better off with Excelsior JET 3.7 and SWT.
  3. snowman

    [Swing Support] In Version 4

    Yes. A complete installer of JEdit made using the current internal build of Excelsior JET 4.0 Pro is 12.8MB if J2SE 1.4.2 profile is used, and 16.0MB is J2SE 5.0 profile is used. These numbers may change in the final version, and will be much higher for the Standard Edition as it will not feature the more effective compression algorithm we'll introduce in 4.0 Pro.
  4. snowman

    Reduce memory usage of application

    I'd suggest that you first experiment with the jet.gc.ratio property - a number of customers have reported good results after they adjusted it. If you have heap size set to "Adaptive", it will never exceed 75% of available physical memory, so as to avoid paging. GC then occurs either when that limit is reached, or periodically according to the jet.gc.ratio setting. This means that on your 1.25GB system with, say, 250MB occupied by the system and other apps, your compiled application will use up to 750MB of memory before GC if you set both jet.gc.heaplimit and jet.gc.ratio to 0 (first setting means adaptive heap size). However, if the system is under heavy load or has little RAM, the use of adaptive heap limit is not recommended in Excelsior JET 3.7. This problem will be addressed in Excelsior JET 4.0, due this fall. It will also have other improvements in the memory manager. FYI: In the Sun HotSpot Client VM 1.4.2, if you do not set -Xmx, heap size is set to 64MB. Not sure about 5.0 and the server VM. For process monitoring, have a look at Process Explorer from SysInternals. It can display lots of useful information about the running processes beside memory use.
  5. snowman

    Reduce memory usage of application

    Check out the Knowledge Base article "HOWTO: Fine tune application memory consumption" What is the value of -Xmx when you run your app on the Sun JRE? Are you using adaptive or fixed heap size in the version compiled by Excelsior JET? How do you measure memory consumption? The most reliable way is to watch Commit Charge in Task Manager's Performance tab. The "Mem Usage" and "VM Size" columns in the Processes tab can show incorrect results. What is the behavior of your application on the same version of the Sun JRE with respect to memory allocation? If it also uses too much memory, we can help you find out what causes it.
  6. snowman

    workstation run time

    You seem to have overlooked the Desktop Runtime, which is royalty-free. The Workstation Runtime is only needed for high-end workstations with two CPU sockets, and only for applications that are designed to take advantage of multiple CPUs. There is no difference in performance between the Desktop Runtime and the Workstation Runtime on a system with one CPU socket, even if the CPU supports HyperThreading or has two cores. There is also no difference on a multi-socket system if your application does not run two or more memory-intensive threads simultaneously. We shall support and improve the Desktop Runtime together with the other runtimes, and it shall remain royalty-free. Excelsior JET Runtime Fee Schedule
  7. snowman

    XDS on Solaris?

    We had XDS-C 2.21 available for Solaris (SPARC), but it has been dropped long ago as we no longer have SPARC hardware. You can use XDS-C for Windows or Linux to cross-compile for Solaris (SPARC) and/or any other platform. Our consultant can help you set up the environment on a hourly basis.
  8. If you look at the above command line, you will notice that gcc is invoked to link the object file produced by xc with the libraries. You can change bin/xc.tem to use ld instead if you wish.
  9. Yes and no. Yes, each of those customers has paid us for customization. See e.g. this press-release to get an idea of what I meant by "customization". And no, they did not implicitely approve distribution to anyone. Most of custom code is under conditional compilation, so it does not get into the generally available binaries.
  10. We have already given XDS away under a freeware license. We may open source it, but please do not expect that to happen in the short term. It would require more work than you problably think. For instance, we have a few customers using custom versions, including native Modula-2 compilers for CPUs other than x86, so we have to ask each of them for permission. If a customer refuses, we would have to remove all the respective customizations from the source.
  11. snowman

    Is this a known compiler bug?

    This restriction sounds natural to me, because: Imagine a general case: somebody have written a program where a series of types T0, T1, T2, etc., are defined in modules A0, A1, A2, etc., respectively, so that Tn+1 extends Tn, and each of Tn has a private field named "f". Now, suppose you decide that for some reason you need a certain field Ti.f exposed for use in some other modules B0, B1, B2, etc. The program won't compile until you refactor either the module Ai, or all modules Aj where j>i.
  12. snowman

    It seems I found a bug... :(

    We have added this issue to our tracking system. If a paying customer asks to fix it, or the whole project gets sponsored, it will be fixed.
  13. snowman

    Call DDL vom Excel VB

    Excelsior JET is essentially a JVM with pre-compilation, otherwise it would not be possible to certify it for compatibility (which we plan to do later this year). So the only way to call a native code DLL from JET-compiled EXE, or call a JET-compiled DLL from a native code EXE is via JNI. In case of VB, JNI does not work directly (in part due to VB runtime launching helper threads without telling anyone ), so you have to use COM wrappers.
  14. xFunction 2.16 for Mac OS X is available for immediate download.
  15. snowman

    language driver interface documentation

    Well, there is not much to think about, the only problem is finding time. I am pressurized to find some contract work ASAP because we have unexpected pauses in two custom projects... I have placed the language drivers source code on our Web site. Enjoy As for open sourcing the entire IDE, I think this is possible but again I cannot make any promises with respect to availability date.
  16. snowman

    SCSL License in Jet 3.8???

    Yes. We also have some ideas on how to shrink it, but that is going to wait until 4.1 or some later version. Right now, our focus in on compatibility, because we need to pass the JCK in order to qualify for the Java Technology license. It will be a commercial license based on SCSL.
  17. We have version 2.32, but we would of course prefer to update it to 2.51. And we would have to repackage it to replace the license agreement anyway. I used to be an OS/2 fan. I believe it would have been superior to XP if IBM continued to work on it. I also like Modula-2. Finally, a very long term supporter of XDS has just asked if we could release the OS/2 version. So I'll try to do something about it. We still have an OS/2 Warp 4 CD and all the necessary tools, and there is a pile of old hardware in the corner of the server room. The only major problem is allocating time to put all those things together, which would also require a total recall. So I'll try to do that but I cannot promise anything with respect to availability time. What is the current status of OS/2? I trust it is completely or mostly dead, no?
  18. That would be difficult as we don't have a single OS/2 box.
  19. snowman

    language driver interface documentation

    Unfortunately, we don't have any documentation for the language support DLLs. We can possibly publish their source code, but note you will need MS Visual C++ to compile them. We are using MSVC 4.2 to build the IDE.
  20. snowman

    Manuals for freeware version?

    I trust you mean printable manuals. They are included in all freeware packages. However, it turned out that our version control system was messed up a little bit. So Native XDS-x86 for Windows and its TSCP add-on were packaged without the printable manuals. We have just refreshed those packages, so if you need the PDFs, just download them again and reinstall.
  21. snowman

    Free personal edition of Excelsior JET 3.7

    The short answer is "no." The long answer is "there going to be special prices on the Standard and Pro Edition for such use, though we cannot say at the moment whether they will be zero." Stay tuned.
  22. snowman

    JRE-indepencency of Jet 3.7

    JRE-independence, as you define it, was supported for a limited class of applications running on J2SE 1.3.x and 1.4.x in JET 3.6 Pro and previous versions. Nothing has changed in version 3.7 in that respect.
  23. Thanks for your purchase! Unfortunately, the answer to your question is negative. You have to recompile the JRE classes. I'd suggest that you use the Eval version for one more day and leave the Pro setup working overnight.