I think everybody should try to identify and learn different code structures. However, in some cases you just can't use these all of the time. For example, at my last job, a college workstudy position, it's expected that the person who takes the job will have taken a few classes in Java, and that's all that can really be expected about their experience. In light of this, I often found myself programming in what I've heard referred to as "programming perl like programming c", or something like that. More relevant to my situation, programming perl like programming java. For most of the stuff I did, it probably could have been done better with a map, or a trailing for, or even something like a Schwarzian Transform, but I just didn't feel right using something like that, because I know that most of the students that will follow me won't really be too perl saavy. I should say I made this assumption by looking at the people who came before me, because their code looked alot like they only knew Java (but hey, maybe they just thought like I did).
I guess that's just an example of sometimes being bound to a certain structure, even if you want to expand more!
-Bryan
In reply to Re: Code Structures
by mrborisguy
in thread Code Structures
by artist
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |