Purpose: Chronic Helicobacter pylori gastritis affects two-thirds of the world's population and is one of the most common chronic inflammatory disorders of humans, the infection clearly results in chronic mucosal inflammation in the stomach and duodenum, which, in turn, might lead to abnormalities in gastroduodenal motility and sensitivity and is the most frequent cause of dyspepsia and peptic disease. Some studies showed that there was a correlation between low-grade inflammation as CRP and HP infection. The purpose of this study was to investigate the relationship between the presence of HP infection and platelet/lymphocyte ratio (PLR). Conclusion: Our study indicated, for the first time, a significant association between HP infection and symptoms based on PLR, a simple and reliable indicator of inflammation. Furthermore, there an increase in PLR as the severity of HP increases. K E Y W O R D SHelicobacter pylori, inflammation, peptic disease, platelet/lymphocyte ratio

Code smells reflect code decay, and, as such, developers should seek to eradicate such smells through application of “deodorant” in the form of one or more refactorings. However, a relative lack of studies exploring code smells either theoretically or empirically when compared with literature on refactoring suggests that there are reasons why smell eradication is neither being applied in anger, nor the subject of significant research. In this paper, we present three studies as supporting evidence for this stance. The first is an analysis of a set of five, open-source Java systems in which we show very little tendency for smells to be eradicated by developers; the second is an empirical study of a subsystem of a proprietary, C# web-based application where practical problems arise in smell identification and the third, a theoretical enumeration of smell-related refactorings to suggest why smells may be left alone from an effort perspective. Key findings of the study were that first, smells requiring application of simple refactorings were eradicated in favour of smells requiring more complex refactorings; second, a wide range of conflicts and anomalies soon emerged when trying to identify smelly code; an interesting result with respect to comment lines was also observed. Finally, perceived (estimated) effort to eradicate a smell may be a key factor in explaining why smell eradication is avoided by developers. The study thus highlights the need for a clearer research strategy on the issue of code smells and all aspects of their identification and measurement.

Code smells represent code decay and as such should be eradicated from a system to prevent future maintenance problems. A range of twenty smells described by Fowler and Beck each require varying numbers and combinations of refactorings in order to be eradicated -but exactly how many are needed when we consider related, nested refactorings is unclear. In this paper, we enumerate these refactorings when categorised according to Mantyla's smell taxonomy. We then show how, ironically, the 'smelliest' of smells (and hence most difficult to eradicate) are actually those best understood by developers. So, code smells are not only unpleasant to have around, but are deceptive in their nature and make-up. The study is thus a warning against attempting to eradicate what are seemingly easily eradicated smells -these are often the smells the developer needs to be most wary of. Finally, we incorporate the answers to six questions suggested by Paul for 'How to write a paper properly' to position the paper in a reflective way.

No abstract

If citing, it is advised that you check and use the publisher's definitive version for pagination, volume/issue, and date of publication details. And where the final published version is provided on the Research Portal, if citing you are again advised to check the publisher's website for any subsequent corrections.