We analyze the types of such behavioral changes caused by current refactoring engines and develop techniques to make them behavior-preserving, ranging from simple techniques to deal with concurrency-related language constructs to a framework that computes and tracks synchronization dependencies. Thus, refactored programs may exhibit unexpected new concurrent behaviors. Assignors: SCHAEFER, MAX, SRIDHARAN, MANU, DOLBY, JULIAN, TIP, FRANK, TORLAK, EMINA Publication of US20110219361A1 publication Critical patent/US20110219361A1/en Application granted granted Critical Publication of US8689191B2 publication Critical patent/US8689191B2/en Status Expired - Fee Related legal-status Critical Current Adjusted expiration legal-status Critical LinksĪutomated refactorings as implemented in modern IDEs for Java usually make no special provisions for concurrent code. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.) Filing date Publication date Application filed by International Business Machines Corp filed Critical International Business Machines Corp Priority to US12/718,648 priority Critical patent/US8689191B2/en Assigned to INTERNATIONAL BUSINESS MACHINES CORPORATION reassignment INTERNATIONAL BUSINESS MACHINES CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Original Assignee International Business Machines Corp Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
( en Inventor Julian Dolby Max Schaefer Manu Sridharan Frank Tip Emina Torlak Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.) Expired - Fee Related, expires Application number US12/718,648 Other versions US20110219361A1 Google Patents Correct refactoring of concurrent softwareĭownload PDF Info Publication number US8689191B2 US8689191B2 US12/718,648 US71864810A US8689191B2 US 8689191 B2 US8689191 B2 US 8689191B2 US 71864810 A US71864810 A US 71864810A US 8689191 B2 US8689191 B2 US 8689191B2 Authority US United States Prior art keywords synchronization dependence source code refactoring behavior Prior art date Legal status (The legal status is an assumption and is not a legal conclusion. Google Patents US8689191B2 - Correct refactoring of concurrent software Look at producer/consumer (assumption is a ProducerConsumer class with two methods).US8689191B2 - Correct refactoring of concurrent software Please send me an email if you have any questions.
If you are not sure which to use, then use notifyAll.Please see explanation that follows. notifyAll should be used most of the time. The following discussion should clear up any doubts. Clearly, notify wakes (any) one thread in the wait set, notifyAll wakes all threads in the waiting set.
0 kommentar(er)
