💡Tips / FAQ
JShell
To quickly test any ch.k43.util function, use the interactive JShell command which is part of the JDK. The jar file ch.k43.util must be in the current directory or a any directory pointed to by the class-path argument.
FAQ
Q: What where the design goals of this Java package ch.k43.util?
Ease of use: The classes and methods must be flexible and simple to use.
No UI calls: Do everything without user interface to allow this toolkit to be used for background tasks or server processes.
Fast: Write the code as performant as possible.
Favor memory usage over I/O: In today's world, memory is no longer a limiting factor. Therefore, many operations can be done in memory where (temporary) files were used in the past (e.g. KDB creates a data structure from SQL SELECT, KFile operations are mostly in memory).
Use extensive logging: The KLog.debug() function is used heavily throughout the code to help debugging your code. Use the toString() methods found in each class to show the internal field values of the objects during development.
Platform independence: Write everything platform independent.
Minimize prerequisites: Stay with the Java SE standard libraries. Use only external JAR files when absolutely necessary (e.g. KSMTPMailer, JDBC drivers).
Q: How many lines of Java code are in this package?
Last updated
