Thanks to everyone, and especially Mars, for thoughtful responses.
Why is it necessary to store this data in code? Seems to me a better approach would be to put the list of constants in some external file and drop it into your project, effectively making a big constant, which you can then load up as an array.
This would indeed be a good idea. I took some of the the code from an open-source blowfish encryption/decryption module, though, and rewriting the method from scratch would be time-consuming. The author may have put the constants in code to make it harder for someone seeking for the initialization constants to find them in the compiled code.
In any case, the solution of dividing the method into two methods works fine for now.
Thanks for the comments, Tom ------------------------------------------------------------- This message has been scanned by Postini anti-virus software. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
