985 resultados para Code provisions
Resumo:
The issuance of the Swiss Federal Act on Collective Investment Schemes (CISA) in the year 2007 and the revision thereof in 2013 expanded the possibilities for restructuring of collective investment schemes and simplified the procedures. For instance, in article 95 the CISA contains a provision that deals in a non-conclusive way with the restructuring of open-ended collective investment schemes. As a novelty regulation, this provision allows for mergers not only of contractual funds but also of investment companies with variable capital (SICAV). Additionally, the transformation of an open-ended collective investment into another CISA legal form was also included into the catalogue of possible restructuring processes. Further, a SICAV still maintains the possibility for asset transfer according to article 69 ff. of the Federal Act on Merger, Demerger, Transformation and Transfer of Assets (MerA). However, not all open questions have been clarified. As long as the CISA does not contain restructuring provisions, as is the case with closed-ended collective investment schemes, generally the MerA and/or the Swiss Code of Obligations (CO) apply. The interplay of diverse, partly overlapping legislative bases leads to the emergence of unwanted gaps. Moreover, the partial revision of the CISA was not completely implemented at the ordinance level. Among others, the following issues have not been conclusively or clearly regulated: the permitted combinations of mergers, the merger procedure of the SICAV, the permitted restructurings, the transformation procedure as well as the application scope of the asset transfer for collective investment schemes according to the relevant merger regulations. Although these questions will be clarified in the following article through a systematic and teleological analysis of the relevant regulations, it is to be hoped that the gaps will be closed within the next CISA revision in order to guarantee comprehensive legal certainty.
Resumo:
Virtual worlds have moved from being a geek topic to one of mainstream academic interest. This transition is contingent not only on the augmented economic, societal and cultural value of these virtual realities and their effect upon real life but also on their convenience as fields for experimentation, for testing models and paradigms. User creation is however not something that has been transplanted from the real to the virtual world but a phenomenon and a dynamic process that happens from within and is defined through complex relationships between commercial and non-commercial, commodified and not commodified, individual and of the community, amateur and professional, art and not art. Accounting for this complex environment, the present paper explores user created content in virtual worlds, its dimensions and value and above all, its constraints by code and law. It puts forward suggestions for better understanding and harnessing this creativity.
Resumo:
Digital technologies have profoundly changed not only the ways we create, distribute, access, use and re-use information but also many of the governance structures we had in place. Overall, "older" institutions at all governance levels have grappled and often failed to master the multi-faceted and multi-directional issues of the Internet. Regulatory entrepreneurs have yet to discover and fully mobilize the potential of digital technologies as an influential factor impacting upon the regulability of the environment and as a potential regulatory tool in themselves. At the same time, we have seen a deterioration of some public spaces and lower prioritization of public objectives, when strong private commercial interests are at play, such as most tellingly in the field of copyright. Less tangibly, private ordering has taken hold and captured through contracts spaces, previously regulated by public law. Code embedded in technology often replaces law. Non-state action has in general proliferated and put serious pressure upon conventional state-centered, command-and-control models. Under the conditions of this "messy" governance, the provision of key public goods, such as freedom of information, has been made difficult or is indeed jeopardized.The grand question is how can we navigate this complex multi-actor, multi-issue space and secure the attainment of fundamental public interest objectives. This is also the question that Ian Brown and Chris Marsden seek to answer with their book, Regulating Code, as recently published under the "Information Revolution and Global Politics" series of MIT Press. This book review critically assesses the bold effort by Brown and Marsden.
Resumo:
Alexandre Weill
Resumo:
Detecting bugs as early as possible plays an important role in ensuring software quality before shipping. We argue that mining previous bug fixes can produce good knowledge about why bugs happen and how they are fixed. In this paper, we mine the change history of 717 open source projects to extract bug-fix patterns. We also manually inspect many of the bugs we found to get insights into the contexts and reasons behind those bugs. For instance, we found out that missing null checks and missing initializations are very recurrent and we believe that they can be automatically detected and fixed.
Resumo:
Code clone detection helps connect developers across projects, if we do it on a large scale. The cornerstones that allow clone detection to work on a large scale are: (1) bad hashing (2) lightweight parsing using regular expressions and (3) MapReduce pipelines. Bad hashing means to determine whether or not two artifacts are similar by checking whether their hashes are identical. We show a bad hashing scheme that works well on source code. Lightweight parsing using regular expressions is our technique of obtaining entire parse trees from regular expressions, robustly and efficiently. We detail the algorithm and implementation of one such regular expression engine. MapReduce pipelines are a way of expressing a computation such that it can automatically and simply be parallelized. We detail the design and implementation of one such MapReduce pipeline that is efficient and debuggable. We show a clone detector that combines these cornerstones to detect code clones across all projects, across all versions of each project.