This is particularly directed to Clint. I am currently going through the Unicon sources (under /uni) and I doing some clean up on the source files. I have noticed that some of the routines are very long. If I split out the code into separate procedures will this have any detrimental effect on the running of the icode files. Is the overhead of calling a routine much greater than just running through the code directly? i have noticed that there are areas that could benefit from a reduction in repeated code in increasing understanding of what the code is doing.
In conjunction to trying to understand the thread structure, I am looking at doing my own personal extension to the Unicon model. This (in my own mind I am calling "polycon"). But before embarking on this journey I am trying to understand the details of the Unicon compiler. With that in mind, I am in the process of trying to simplify some of the code, things like changing long nested if statements to case of statements, decreasing the size of the longer routines, changing some of the shorter routines to be more idiomatic etc. Is any of this going to be useful to others or should I keep this well out of the way of what you are doing? So as to not interfere with the directions that you are proceeding in. regards Bruce Rennie ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Unicon-group mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unicon-group
