Have you considered making properties first-class Objects? This could lead to greatly simplified code. Consider
package EmmisiveColor;
sub new {
my $pkg = shift;
return bless [ @_ ], $pkg;
}
sub as_string {
my $self = shift;
"emmisiveColor @$self"
}
And so on for the other properties.
Properties become easier to enumerate. You can do away with the switch entirely. Assuming you're doing so within the context of an object that holds properties,
your snippet reduces to something like:
sub simple_properties {
my $self = shift;
my @propstrings = map { $_->as_string() } $self->properties();
return
"appearance Appearance {\n" .
" material Material {\n" .
" ", join("\n ", @propstrings), "\n" .
" }\n" .
"}\n";
}
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.