Hello Carnë, Yes, i think it can be made a subfunction. The thing is, the dictionary from huffmandict() is very efficient for encoding and memory-wise, but the array-tree is good at decoding but not memory-efficient. Embedding dict2tree into huffmandeco seems like a good idea.
I copied the license-help and input validation from the "old" huffmandeco because I wasn't aware newer functions use GPLv3+, but you can change it if you want, no problem. Same for error-checking, print_usage() makes more sense. I made the following changes: - Made dict2tree into a subfunction. - Changed license text to v3+. - Made invalid input print the function usage. Let me know if anything else should be changed. Thank you, Ferran http://gnu-octave-repository.2306053.n4.nabble.com/file/n4166953/huffmandeco.m huffmandeco.m -- View this message in context: http://gnu-octave-repository.2306053.n4.nabble.com/Fwd-Request-to-join-as-developer-Submission-to-Communications-package-tp4155598p4166953.html Sent from the octave-dev mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
