OT, but I'd use a datastructure to represent your equation constants in a table, and then have an algorithm calculate things based on that table and the input parameters.
The if-comb is fine for simple things, but as the problem grows in complexity you're going to need to keep adding more if's. Treating the model as data instead of code will make things easier in the long run, but takes a little more work initially.
I'll leave building that datastructure up to you, but in my world an if-comb typically (but not always) represents a design that could be improved to be more algorithmic. A particularly noteable point is a variable such as '$ratioincome28', which probably should not exist as a named variable in your program. Rather, that value might exist as an array value at index 28 or (better?) a hash key/value pair.
In all, it's about maintainability and good coding practices for long term coding.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||