Decompiling

decompilers (fail to) work as such: find which architecture -> disassemble -> pattern finder/search for common code segments/idioms, language dependent -> turn into higher level code. it would seem to me what is needed is a good database of the high-level -> assembly idioms, that the decompiler accesses at run time and is always updated as new links are found (thinking that the decompiler would be part of a suite with other tools to help find these links). how many different ways do different compilers really have available to make "if(a==b)"? and more complex code is just combination of these smaller parts. assuming they optimize when compiling, that's what's really needed, a way to keeping track of these different ways of doing the same thing, slight variations, etc., and of course a way to find them in the first place (the suite i mentioned, which i also have ideas for; properly formatted assembly for starters). i don't get why decompilers don't work.

For both PC- and NPC-oriented students, the diagnostic and patient-related characteristics of their preferred specialties were highly influential. PC-oriented students were more likely to be attracted to prevention and biopsychosocial aspects of specialties, and NPC-oriented students to the opportunity to do procedures and intervene in illnesses. Student gender appeared to have little influence on response patterns, except as a proxy for specialty preference, which, for women, was more likely to be a primary care specialty.