TL;DR: Cyclone as discussed by the authors is a type-safe programming language derived from C. The primary design goal of Cyclone is to let programmers control data representation and memory management without sacrificing type-safety.
Abstract: Cyclone is a type-safe programming language derived from C. The primary design goal of Cyclone is to let programmers control data representation and memory management without sacrificing type-safet...
TL;DR: In this article, a system filling of worked out spaces for the mining industry is described. But this method is applicable at enterprise including concentrating mill and mining minerals by system filling system filling.
Abstract: mining industry SUBSTANCE: method is applicable at enterprise including concentrating mill and mining minerals by system filling of worked out spaces Method includes supply of tailings of concentrating mill through circular pipeline with possibility of direction into several filling complexes located successively over its length A part of tailings at each filling complex is directed from circular pipeline and separated in hydraulic cyclone into sands and overflow Separated from hydraulic cyclone overflow is thinned product which is supplied together with hydraulic cyclone sands for forming of filling mixture, and overflow is returned to circular pipeline Formed in mixer is filling mixture from sands, thinned product and additives EFFECT: provided year-round transportation of tailings of concentrating mill for low-cost preparation of filling mixture for several users 1 dwg
TL;DR: Cyclone is an experimental, type-safe programming language based upon the syntax, semantics, and spirit of C that is designed to provide a type- safe environment that is c...
Abstract: Cyclone [1, 2] is an experimental, type-safe programming language based upon the syntax, semantics, and spirit of C. The primary goal of the language is to provide a type-safe environment that is c...
TL;DR: In this paper, the authors proposed a method for manufacturing a multi-cell cyclone with a plurality of cylone cells which provide the optimum separation effect and continuous period at a reasonable cost.
Abstract: PROBLEM TO BE SOLVED: To provide a multi-cell cyclone provided with a plurality of cylone cells which provide the optimum separation effect and continuous period at a reasonable cost and a method for manufacturing the multi-cell cyclone. SOLUTION: Cyclone cells of a multi-cell cyclone are assembled in groups and the groups are sucked through a route composing part. Accordingly, better suction control can be carried out. The suction can be carried out, for example, through a common aperture 19 formed in a group 21 of group cyclone cells. Further, the cyclone cell groups are produced in form of a module and the module can be composed by assembling, for example, two members 12 and 13. At that time, similar constituent elements of the cyclone cell groups are integrated in a single member. Consequently, an efficient separation effect can be obtained by taking shortened assembly time and manufacturing cost. COPYRIGHT: (C)2003,JPO
TL;DR: A combination of default annotations, local type inference, and a novel treatment of region effects reduces this burden and integrates C idioms in a region-based frame- work of Cyclone.
Abstract: Cyclone is a type-safe programming language derived from C. The primary design goal of Cyclone is to let program- mers control data representation and memory management without sacrificing type-safety. In this paper, we focus on the region-based memory management of Cyclone and its static typing discipline. The design incorporates several ad- vancements, including support for region subtyping and a coherent integration with stack allocation and a garbage col- lector. To support separate compilation, Cyclone requires programmers to write some explicit region annotations, but a combination of default annotations, local type inference, and a novel treatment of region effects reduces this burden. As a result, we integrate C idioms in a region-based frame- work. In our experience, porting legacy C to Cyclone has required altering about 8% of the code; of the changes, only 6% (of the 8%) were region annotations.
TL;DR: The Cyclone type system is summarized and the analysis issues that arise in its implementation are focused on, including (a) kind and type inference, (b) region and effect inference, and (c) dataflow analysis for validating initialization, array subscripts, and linear pointers.
Abstract: Cyclone [1, 2] is an experimental, type-safe programming language based upon the syntax, semantics, and spirit of C. The primary goal of the language is to provide a type-safe environment that is close enough to C in both appearance and functionality, that systems programmers will find it attractive and useful.The most challenging aspect of the design is capturing the spirit of C without compromising type-safety. In particular, systems programmers expect to have good control over data representations, memory management, and performance. Yet, these features are usually absent from high-level, type-safe languages (e.g., Java). Another challenge is validating a sufficiently wide set of idioms that are in fact type-safe, but which conventional type systems reject.To address these issues, we have used a novel combination of typing features in conjunction with some interesting inference and dataflow techniques. The most novel typing feature is the support for region-based memory management which was summarized in an earlier paper [1]. However, this paper did not discuss the inference techniques we use to validate the regions and effects.In this talk, I will briefly summarize the Cyclone type system and then focus on the analysis issues that arise in its implementation, including (a) kind and type inference, (b) region and effect inference, and (c) dataflow analysis for validating initialization, array subscripts, and linear pointers.
TL;DR: This paper examines safety violations enabled by C’s design, and shows how Cyclone avoids them, without giving up C”s hallmark control over low-level details such as data representation and memory management.
Abstract: Cyclone is a safe dialect of C. It has been designed from the ground up to prevent the buffer overflows, format string attacks, and memory management errors that are common in C programs, while retaining C’s syntax and semantics. This paper examines safety violations enabled by C’s design, and shows how Cyclone avoids them, without giving up C’s hallmark control over low-level details such as data representation and memory management.
TL;DR: This paper focuses on the region-based memory management of Cyclone and its static typing discipline, and combines default annotations, local type inference, and a novel treatment of region effects to reduce this burden.
Abstract: Cyclone is a type-safe programming language derived from C. The primary design goal of Cyclone is to let programmers control data representation and memory management without sacrificing type-safety. In this paper, we focus on the region-based memory management of Cyclone and its static typing discipline. The design incorporates several advancements, including support for region subtyping and a coherent integration with stack allocation and a garbage collector. To support separate compilation, Cyclone requires programmers to write some explicit region annotations, but a combination of default annotations, local type inference, and a novel treatment of region effects reduces this burden. As a result, we integrate C idioms in a region-based framework. In our experience, porting legacy C to Cyclone has required altering about 8% of the code; of the changes, only 6% (of the 8%) were region annotations.