Is the Decision to Code-Share a Route Different for Virtual and Traditional Code-Share Arrangements

This paper analyzes factors that determine whether alliance carriers choose to remain in or leave a code-share agreement on individual routes. Different types of code-sharing are considered: traditional code-shared routes, virtual code-shared routes and those routes with both traditional and virtual code-sharing. Empirical results show that factors affecting alliance firms’ code-sharing decisions significantly differ for virtual versus traditional code-share agreements. Virtual code-sharing tends to take place in less dense markets and is not significantly affected by yields. This provides tentative support for the Ito and Lee (2005) argument that virtual code-sharing provides a mechanism by which carriers practice price discrimination (for instance, filling unoccupied seats in less dense markets). In contrast traditional code-sharing is found to be more likely to occur in dense markets and higher yields increase the probability of such arrangements. Thus, traditional code-sharing seems to be used to achieve the networking economics and cost savings derived from dense markets and thus appears to be more effective as an instrument to introduce competition into a market

Stack Overflow: A Code Laundering Platform?

Developers use Question and Answer (Q&A) websites to exchange knowledge and expertise. Stack Overflow is a popular Q&A website where developers discuss coding problems and share code examples. Although all Stack Overflow posts are free to access, code examples on Stack Overflow are governed by the Creative Commons Attribute-ShareAlike 3.0 Unported license that developers should obey when reusing code from Stack Overflow or posting code to Stack Overflow. In this paper, we conduct a case study with 399 Android apps, to investigate whether developers respect license terms when reusing code from Stack Overflow posts (and the other way around). We found 232 code snippets in 62 Android apps from our dataset that were potentially reused from Stack Overflow, and 1,226 Stack Overflow posts containing code examples that are clones of code released in 68 Android apps, suggesting that developers may have copied the code of these apps to answer Stack Overflow questions. We investigated the licenses of these pieces of code and observed 1,279 cases of potential license violations (related to code posting to Stack overflow or code reuse from Stack overflow). This paper aims to raise the awareness of the software engineering community about potential unethical code reuse activities taking place on Q&A websites like Stack Overflow.Comment: In proceedings of the 24th IEEE International Conference on Software Analysis, Evolution, and Reengineering (SANER

simecol: An Object-Oriented Framework for Ecological Modeling in R

The simecol package provides an open structure to implement, simulate and share ecological models. A generalized object-oriented architecture improves readability and potential code re-use of models and makes simecol-models freely extendable and simple to use. The simecol package was implemented in the S4 class system of the programming language R. Reference applications, e.g. predator-prey models or grid models are provided which can be used as a starting point for own developments. Compact example applications and the complete code of an individual-based model of the water flea Daphnia document the efficient usage of simecol for various purposes in ecological modeling, e.g. scenario analysis, stochastic simulations and individual based population dynamics. Ecologists are encouraged to exploit the abilities of simecol to structure their work and to use R and object-oriented programming as a suitable medium for the distribution and share of ecological modeling code.

The Right to Code and Share Arms

Glycerol is, to date, the most widely used cryoprotectant to freeze stallion spermatozoa at concentrations between 2% and 5%. Cryoprotectant toxicity has been claimed to be the single most limiting factor for the success of cryopreservation. In order to evaluate the toxic effects of the concentrations of glycerol used in practice, stallion spermatozoa were incubated in Biggers Whitten and Whittingham (BWW) media supplemented with 0%, 0.5%, 1.5%, 2.5%, 3.5%, and 5% glycerol. In two additional experiments, a hyposmotic (75 mOsm/kg) and a hyperosmotic (900 mOsm/kg) control media were included. Sperm parameters evaluated included cell volume, membrane integrity, lipid peroxidation, caspase 3, 7, and 8 activation, mitochondrial membrane potential, and integrity of the cytoskeleton. Glycerol exerted toxicity at concentrations 3.5% and the maximal toxicity was observed at 5%. The actin cytoskeleton was especially sensitive to glycerol presence, inducing rapid F actin depolymerization at concentrations over 1.5%. The sperm membrane and the mitochondria were other structures affected. The toxicity of glycerol is apparently related to osmotic and nonosmotic effects. In view of our results the concentration of glycerol in the freezing media for stallion spermatozoa should not surpass 2.5%.Funding Agencies|Ministerio de Ciencia e Innovacion-FEDER Madrid, Spain|AGL 2010 20758 (GAN)|Inia|RZ2008-00018-00-00|Junta de Extremadura FEDER GR|10010

Neural Machine Translation Inspired Binary Code Similarity Comparison beyond Function Pairs

Binary code analysis allows analyzing binary code without having access to the corresponding source code. A binary, after disassembly, is expressed in an assembly language. This inspires us to approach binary analysis by leveraging ideas and techniques from Natural Language Processing (NLP), a rich area focused on processing text of various natural languages. We notice that binary code analysis and NLP share a lot of analogical topics, such as semantics extraction, summarization, and classification. This work utilizes these ideas to address two important code similarity comparison problems. (I) Given a pair of basic blocks for different instruction set architectures (ISAs), determining whether their semantics is similar or not; and (II) given a piece of code of interest, determining if it is contained in another piece of assembly code for a different ISA. The solutions to these two problems have many applications, such as cross-architecture vulnerability discovery and code plagiarism detection. We implement a prototype system INNEREYE and perform a comprehensive evaluation. A comparison between our approach and existing approaches to Problem I shows that our system outperforms them in terms of accuracy, efficiency and scalability. And the case studies utilizing the system demonstrate that our solution to Problem II is effective. Moreover, this research showcases how to apply ideas and techniques from NLP to large-scale binary code analysis.Comment: Accepted by Network and Distributed Systems Security (NDSS) Symposium 201

A critical analysis of the Ethiopian Commercial Code in light of OECD Principles of Corporate Governance

This dissertation critically analyzes whether the current Ethiopian share company law (part of the Commercial Code) envisaged such outcomes or not by using the six key minimum standards of OECD Principles of corporate governance as a template. It demonstrates how the legal and regulatory framework of the share company law provisions apparently has failed to create incentives for market players and also failed to promote transparent and efficient market. To smooth the progress of new investment and provide adequate investors’ protection, this dissertation recommends Ethiopia should revisit and update its share company law in light of the relevant OECD Principles by taking into account its own legal, economic and cultural circumstances

Untangling Fine-Grained Code Changes

After working for some time, developers commit their code changes to a version control system. When doing so, they often bundle unrelated changes (e.g., bug fix and refactoring) in a single commit, thus creating a so-called tangled commit. Sharing tangled commits is problematic because it makes review, reversion, and integration of these commits harder and historical analyses of the project less reliable. Researchers have worked at untangling existing commits, i.e., finding which part of a commit relates to which task. In this paper, we contribute to this line of work in two ways: (1) A publicly available dataset of untangled code changes, created with the help of two developers who accurately split their code changes into self contained tasks over a period of four months; (2) a novel approach, EpiceaUntangler, to help developers share untangled commits (aka. atomic commits) by using fine-grained code change information. EpiceaUntangler is based and tested on the publicly available dataset, and further evaluated by deploying it to 7 developers, who used it for 2 weeks. We recorded a median success rate of 91% and average one of 75%, in automatically creating clusters of untangled fine-grained code changes