Slices & Articles Get by the slice or add to your own ebook
|Shirazi, Jack||O'Reilly Media|
In this chapter:
• Garbage Collection
• Tuning the Heap
• Sharing Memory
• Replacing JDK Classes
• Faster VMs
• Better Optimizing Compilers
• Native Method Calls
• Uncompressed ZIP/JAR Files
Throughout the progressive versions of Java, improvements have been made at all levels of the runtime system: in the garbage collector, in the code, in the VM handling of objects and threads, and in compiler optimizations. It is always worthwhile to check your own application benchmarks against each version (and each vendor’s version) of the Java system you try out. Any differences in performance need to be identified and explained; if you can determine that a compiler from one version (or vendor) together with the runtime from another version (or vendor) speeds up your application, you may have the option of choosing the best of both worlds. Standard Java benchmarks tend to be of limited use in deciding which VMs provide the best performance for your application. You are always better off creating your own application benchmark suite for deciding which VM and compiler best suit your application.See All Chapters
|Simon St. Laurent||O'Reilly Media||ePub|
In Chapter 2, you learned how to add documentation to your programs. The ExDoc tool takes that documentation and produces nicely formatted reference documentation in web page format. ExDoc works in conjunction with Mix, a tool for creating, compiling, and testing projects.You can find out more about Mix in Chapter 12.
The easiest way to create documentation is to create a project using the
Here is what it looks like when creating the documentation for the code in Example 2-4.
Change to the combined directory and put all of your source files (for this example, combined.ex, drop.ex, and convert.ex) into the lib directory. The combined.ex file you have written before will replace the one in that mix created for you in the lib directory.
Now edit the file mix.exs so that the
|Michael Balint||Karnac Books||ePub|
ONE, perhaps the eternal, ambition of art is to represent life (or perhaps nature) as faithfully and sincerely as possible. (In order to avoid possible misunderstanding I wish to emphasise that life and nature are meant to include the inner world of the artist.) There are, however, some inherent limitations to faithfulness in all forms of artistic representation: (a) it Is only possible to represent a certain part or parts of life or nature, never the whole; (b) the representation, however faithful and sincere, can never be life itself; it is always a reconstruction, never the original.
These two inevitable limitations induce the artist to be arbitrary, wilful or even wanton: he must choose the part or parts of life to be represented, and he must choose his way of representing the qualities, elements, features, etc., that he feels to be essential. The two demands, faithfulness and sincerity on the one hand, arbitrary choice of theme and the way of representing its essential elements on the other, can hardly be reconciled. Perhaps the whole history of art, and certainly the history of art since the Renaissance, can be viewed as a series of different attempts at solving this insoluble dilemma.See All Chapters
|Rob Brooks-Bilson||O'Reilly Media||ePub|
In 1989, two chemists, Martin Fleischmann and Stanley Pons, claimed that their research had uncovered a phenomenon that promised to solve the world’s energy problems. What they claimed to have accomplished was nothing short of astonishing: that they had achieved nuclear fusion at room temperature. They called their discovery cold fusion. Unfortunately, the scientific community at large dismissed their findings because no one was ever able to reproduce the results claimed in the original experiment. Oh wait, wrong book...
In 1995, J.J. and Jeremy Allaire introduced a product they believed would revolutionize application development for the Web. They too called their creation ColdFusion. The two brothers formed the Allaire Corporation and began selling ColdFusion. Unlike its infamous namesake, ColdFusion has delivered on the promises put forth by its creators. In 2001, Macromedia acquired Allaire, and along with it, ColdFusion. ColdFusion MX represents the second ColdFusion product release under the Macromedia banner.See All Chapters
|Simon Cozens||O'Reilly Media||ePub|
Every programmer likes writing code, but only a brave and masochistic few actually like writing tests for their code. However, with the rise of XP, Agile programming, and other programming methodologies, it has become more important for programmers to write complete test suites for the code they produce.
Not only that, but thanks to the efforts of the Perl Kwalitee Assurance team, headed by Michael Schwern, there's a good deal of social pressure for CPAN module writers to come up with thorough automated test plans for their modules.
Thankfully, Schwern and others have also produced a bunch of modules that make producing such test plans relatively painless. We'll take a look at the more popular and useful modules in this chapter.
Back in the mists of time, around the late 1990s, test plans were very simple indeed; you had a program that spat out "ok" or "not ok" followed by a test number, and an automated testing harness would go through, run your tests, and pick out the tests that failed.See All Chapters
Business & Economics