|
|
Brock LaMeres
HW#13
1. what do you consider the main message of the paper?
This paper presented a pretty neat way of getting software developers an easy way to re-use code. This is very similar to a critic system where suggestions are made. While this sounds great, software developers may be reluctant to use this system due to misunderstanding.
2. how is this work applicable to your own
2.1. work?
I do not do straight software coding at my job but I am involved in FPGA developement from time to time. FPGA design is some using high level languages such as Verilog. We use a related system at Agilent where we use EMACS's RCI feature to assist in the FPGA development. A common problem in Hardware description is where you are trying to describe a boolean function. If every possible value of the input variables is not explicitly described, then a memory eliment will be synthesis'd. We use EMACS to automatically generate all of the variable states whenever write text that looks like we are trying to form a boolean expression. An example would be:
always @ (var1 or var2 or var3)
2.2. interests?
I see much value in this, specifically in FPGA design.
3. do you have ideas how the work in the paper could or should be further developed?
I would like to see study's in real environment. For example, somebody who is developing an actual product and is under schedule constraints. If there were real benifits, then this environment would show them because the project would come in early.
4. have you used any reuse libraries
4.1. if not: why not?
No, I don't code at my current job. I have used the EMACS feature I described above.
4.2. if yes: which ones? did the libraries have any particular strengths and weaknesses?
N/A
5. How does Codebroker infer the "task-at-hand"?
It depends on the "end of comment" syntax. It then goes back and looks for a signiture.
6. what are the trade-offs between
6.1. to let the systems infer the task-at-hand
It depends on a particular comment/code structure. If the developer is using an unorthodox coding style, CodeBroker might now pick up the desired operation.
6.2. versus that the users specifies the task at hand?
This takes time and has the same problems that looking up classes/syntax has. The developer may not know that what he is trying to do has a name so he will not know how to specify it.
|
|