DashO can also statically analyze the code to find unused types, methods, and fields, and delete them, thereby making the application smaller. DashO can delete used methods that are not needed in published applications, such as debugging and logging calls.
^Hamilton, James; Danicic, Sebastian (2011). "An evaluation of the resilience of static java bytecode watermarks against distortive attacks". IAENG International Journal of Computer Science. 38 (1). International Association of Engineers: 1–15.
^Patki, Tapasya (2008). "Dasho java obfuscator". Department of Computer Science. University of Arizona.
^J. MacBride; Christopher J Mascioli; Scott Marks; Ying Tang; L. Head; P. Ramachandran (2005). "A Comparative Study of Java Obfuscators". Proceedings of the IASTED International Conference on Software Engineering and Applications.
^Park, Jonghwa; Kim, Hyojung; Jeong, Younsik; Cho, Seong-je; Han, Sangchul; Park, Minkyu (2015). "Effects of Code Obfuscation on Android App Similarity Analysis". J. Wirel. Mob. Networks Ubiquitous Comput. Dependable Appl. 6 (4): 86–98.