The generation of hydrogen peroxide (H2O2) and hydroxyl radical (HO˙) during the oxidation of l-ascorbic acid (l-AA) by oxygen with copper as a catalyst.

No abstract

No abstract

No abstract

No abstract

IntelliMerge: A Refactoring-Aware Software Merging Technique 170:3 generality and efficiency of automatic conflicts resolving by combining unstructured and structured approaches. These approaches can also be classified as textual, syntactic and semantic approaches, according to the extent they make use of the semantic information in the source code [Mens 2002]. However, most of the existing approaches still fail to deal with one kind of complex changes made to source code, namely, the refactorings. In general, a refactoring change to a program denotes a transformation to the program (e.g., Rename/Move Field and Extract/Inline Method) that improves the program's internal design without changing its externally observable behavior [Fowler 2002]. Complex refactorings usually consist of a set of related changes across multiple source code files in the program. As an important kind of change in object-oriented programming (OOP) and agile development, refactorings are widespread in software development and evolution [Fowler 2002]. The automated refactoring tools also contribute to the popularity of refactorings since these tools allow programmers to apply refactoring quickly and safely [Dig et al. 2007]. However, it has been observed that refactoring is one of the main factors that make trouble to unstructured merge techniques [Dig et al. 2006a, 2007]. A recent empirical study [Mahmoudi et al. 2019] on about 3,000 open-source Java projects also concludes that (1) at least 22% of merge conflicts are related to refactoring, and (2) these conflicts are more complex and difficult to resolve comparing with those refactoring-irrelevant conflicts. On one hand, a refactoring often affect multiple parts of the program, but most existing approaches do not consider the possible dependencies between different changes in the merging process; on the other hand, refactoring-related conflicts are more difficult for developers to understand and resolve, because of the absence of the refactoring history [Tsantalis et al. 2018].

No abstract

No abstract