Help Center
Local Navigation
- Understanding BlackBerry and programming for BlackBerry devices
- BlackBerry Java Application design
- Standalone applications
- Applications with desktop synchronization
- Applications with wireless access, wireless synchronization, or wireless alerting
- MIDlet applications
- CLDC applications
- API control and code signing
- Object modeling
- Multithreading
- Best practices for writing an efficient BlackBerry Java Application
- Best practice: Writing efficient code
- Using local variables
- Using shorthand for evaluating Boolean conditions
- Making classes final
- Using int instead of long
- Avoiding garbage collection
- Using static variables for Strings
- Avoiding the String(String) constructor
- Writing efficient loops
- Optimizing subexpressions
- Optimizing division operations
- Avoiding java.util.Enumeration
- Performing casts using instanceof
- Evaluating conditions using instanceof
- Avoiding StringBuffer.append (StringBuffer)
- Avoiding returning null
- Avoiding passing null into methods
- Using caution when passing null into a constructor
- Using longs for unique identifiers
- Exiting applications correctly
- Printing the stack trace
- Best practice: Using objects judiciously
- Best practice: Reducing the size of compiled code
- Best practice: Writing efficient code
- Multilanguage support
- Multimedia support
- UI and navigation design
- Memory management
- Data management
- Wireless data transport
- BlackBerry application integration
- Security considerations
- Test a BlackBerry Java Application
- Making applications available
- Glossary
- Legal notice
BlackBerry Manuals & Help
>
Documentation for Developers
>
Java Development Guides and API Reference
>
Fundamentals Guide - BlackBerry Java Development Environment - 4.7.0
Exiting applications correctly
Before you invoke System.exit(int status), perform any necessary cleanup, such as removing objects from the runtime store that applications no longer require.
Parent topic: Best practice: Writing efficient code