Type Analysis for JavaScript

Pediatric Oncology Clinic Care Model: How to Care for Patients to Achieve Better Continuity of Care in a Medium Sized Program

Text entry system can be found commonly in modern computer and mobile devices such as smartphone and tablet. However, most of these systems are not easily operable by the handicapped; the system either has small area size of each key or requires major hand movement, such as in the case of the common QWERTY keyboard that contains over a hundred keys. All of these present systems are less than ideal for the handicapped to use as input device. In this paper, a new wireless text entry system is proposed to help the handicapped people to input text efficiently with minimum hand movement. From the design of the prototype, it is smaller than the traditional keyboard, portable, lightweight, user friendly, and long operating hours with built-in mouse function. Practically, it is tested and proven that only one hand is needed to hold the equipment and one finger to interact as well as to input the text. The algorithm used is: Press-Drag-Release algorithm, namely the user just need to presses on the infrared board, followed by finger dragging around the board for letter selection, and lastly, releasing of finger for input the letter. From the result of experiments, the proposed system was tested and proven portable (7.5cm × 5.5cm × 5.5cm), lightweight (100 grams excluding battery), user-friendly with many built-in functions (Esc, Copy, Cut, Paste, Ctrl-A, and Mouse), and long operating hours (29.4 hours operating time with 10,000 mAH battery). For Words Per Minute (WPM), the experiment shows that it can achieve as high as 5 to 10 WPM depends on the skillfulness of the user.

: RED is a programmed language designed, in accordance with the DOD steelman requirements, for DoD embedded computer applications. The language combines features common to most existing high level languages with new capabilities for abstract data types, exception handling, multitasking, generic definitions and access to machine-dependent facilities. This manual covers lexical structures, program structures, types, expression, statements, procedures, functions and parameters, capsules, exception handling, multitasking, overloading and generics, machine dependent facilities, advanced definitions, and low level facilities. The RED language has been designed to reduce the total life cycle cost of designing, implementing, testing, and maintaining programs. For small and medium size programs, most modern high level languages are similar. However, for large programs, such as those commonly developed for embedded applications, the facilities provided by a language become crucial. What distinguishes the RED language is that it makes it easy to express solutions to the problems encountered when developing large programs.

A typestate property describes which operations are available on an object or a group of inter-related objects, depending on this object’s or group’s internal state, the typestate. Researchers in the field of static analysis have devised static program analyses to prove the absence of typestate-property violations on all possible executions of a given program under test. Researchers in runtime verification, on the other hand, have developed powerful monitoring approaches that guarantee to capture property violations on actual executions. Although static analysis can greatly benefit runtime monitoring, up until now, most static analyses are incompatible with most monitoring tools. We present Clara, a novel framework that makes these approaches compatible. With Clara, researchers in static analysis can easily implement powerful typestate analyses. Runtime-verification researchers, on the other hand, can use Clara to specialize AspectJ-based runtime monitors to a particular target program. To make aspects compatible to Clara, the monitoring tool annotates them with so-called dependency state machines. Clara uses the static analyses to automatically convert an annotated monitoring aspect into a residual runtime monitor that is triggered by fewer program locations. If the static analysis succeeds on all locations, this proves that the program fulfills the stated typestate properties, making runtime monitoring entirely obsolete. If not, the residual runtime monitor is at least optimized. We instantiated Clara with three static typestate analyses and applied these analyses to monitoring aspects generated from tracematches. In two-thirds of the cases in our experiments, the static analysis succeeds on all locations, proving that the program fulfills the stated properties, and completely obviating the need for runtime monitoring. In the remaining cases, the runtime monitor is often significantly optimized.

Secure Programming Guidelines help to prevent developers from introducing vulnerabilities. But being just static text to be consulted now and then, the Guidelines are difficult to integrate in the implementation phase of software development, especially when developers are under pressure of delivering software for a deadline. In this paper, we present an IDE integration of security testing and static code analysis to detect vulnerabilities and known insecure coding patterns according to Secure Programming Guidelines. While security testing tools and static analyzers exist for security professionals, similar tools to be used by software engineers who are normally non security experts are missing. This automated tool support is non-intrusive during implementation by being fully integrated in the IDE developers use, efficient to not slow down the overall implementation effort, and extensible to consider different vulnerabilities. We implement this IDE integration as an extension to SAP HANA Web-based Development Workbench. While not proposing new security testing nor static code analysis techniques, we integrate multiple security analysis to make them usable for developers during implementation, as they are relevant threats to SAP HANA applications and thus concerned in the Secure Programming Guidelines.

Static program analyses and transformations for Java face many problems when analyzing programs that use reflection or custom class loaders: How can a static analysis know which reflective calls the program will execute? How can it get hold of classes that the program loads from remote locations or even generates on the fly? And if the analysis transforms classes, how can these classes be re-inserted into a program that uses custom class loaders?

A practical algorithm for learning disjunctive abstraction heuristics in static program analysis

Experimental data and correlations are not available for the fuel-assembly concept of the Canadian supercritical water-cooled reactor (SCWR). To facilitate the safety analyses, a strategy for developing a heat-transfer correlation has been established for the fuel-assembly concept at supercritical pressure conditions. It is based on an analytical approach using a computational fluid dynamics (CFD) tool and the ASSERT subchannel code to establish the heat transfer in supercritical pressure flow. Prior to the application, the CFD tool was assessed against experimental heat transfer data at the pseudocritical region obtained with bundle subassemblies to identify the appropriate turbulence model for use. Beyond the pseudocritical region, where the normal heat transfer behavior is anticipated, the ASSERT subchannel code also was assessed with appropriate closure relationships. Detailed information on the supporting experiments and the assessment results of the computational tools are presented.

Static analysis of multi-staged programs is challenging because the basic assumption of conventional static analysis no longer holds: the program text itself is no longer a fixed static entity, but rather a dynamically constructed value. This article presents a semantic-preserving translation of multi-staged call-by-value programs into unstaged programs and a static analysis framework based on this translation. The translation is semantic-preserving in that every small-step reduction of a multi-staged program is simulated by the evaluation of its unstaged version. Thanks to this translation we can analyze multi-staged programs with existing static analysis techniques that have been developed for conventional unstaged programs: we first apply the unstaging translation, then we apply conventional static analysis to the unstaged version, and finally we cast the analysis results back in terms of the original staged program. Our translation handles staging constructs that have been evolved to be useful in practice (typified in Lisp's quasi-quotation): open code as values, unrestricted operations on references and intentional variable-capturing substitutions. This article omits references for which we refer the reader to our companion technical report.

Introduction This study explores the attitudes of students and teachers toward home language (HL) integration in English as an Additional Language (EAL) classrooms in Norway. As multilingualism becomes increasingly visible in Norwegian schools, the traditional emphasis on monolingual, target-language (TL)-only instruction is being questioned. Methods Drawing on data from classroom observations and semi-structured interviews with six EAL teachers and 32 students across three linguistically diverse lower secondary schools, this study examines how HL use is perceived, enacted, and negotiated in practice. Results The findings highlight two central themes. First, both students and teachers demonstrated a strong ideological commitment to English as the primary language of instruction. Teachers frequently positioned themselves as gatekeepers of TL exposure, citing institutional expectations and professional norms that prioritize English-only approaches. Similarly, students—especially in the upper grades—viewed TL immersion as essential preparation for exams and future opportunities. However, classroom practices often deviated from these ideological positions. Teachers routinely used HLs, particularly Norwegian, for clarification, translation, and classroom management, especially in mixed-ability settings. Students also identified HL use as helpful for reducing stress, boosting comprehension, and making abstract concepts more accessible. While English remained the main instructional language, HLs were valued as supportive tools rather than threats to learning. The second theme concerns the constraints and uncertainties limiting systematic multilingual implementation. Teachers reported feeling underprepared and unsupported when drawing on students’ broader linguistic repertoires. While many recognized the benefits of HL integration, they voiced concerns about time, fairness, and feasibility, particularly when students’ HLs differed from their own. Students, too, expressed mixed feelings: while many supported HL use, some worried it might highlight linguistic differences or create divisions. Discussion Overall, the study suggests that HL integration is not a binary choice but a dynamic, context-dependent negotiation. The findings underscore the need for clearer policy frameworks, targeted teacher training, and classroom-based examples to support inclusive language teaching. By foregrounding the voices of both teachers and learners, the study contributes to ongoing discussions on how multilingualism can be meaningfully integrated into EAL pedagogy in Norway and similar contexts.

Interaction testing aims at identifying faults that arise due to combinations of values. It requires testing of all possible t-way tuples, which is an expensive task. It might be the case that testing of all t-way tuples is not required as only few of them are fault triggering while most of them are not. In the past, researchers have proposed an approach to identify interactions that may cause failure using data flow technique. The gain was restricted as the approach was manual and no tool support was provided. Till date, there does not exist any tool that can identify interaction faults using static analysis. In this paper, an attempt is made to automate the process of identifying probable interactions that exist in the source code by designing a tool: Failure Triggering Combinations Identifier (FTCI). Two case studies have also been taken in order to show the working of the tool. Results indicate that the tool is able to successfully identify interaction faults.

Metamodels are often augmented with additional constraints that must be satisfied by valid instances of these metamodels. Such constraints express complex conditions that cannot be expressed in the metamodel itself. Model transformations have to take such constraints of the source and target metamodels into account. Given a valid source model, which satisfies the source constraints, a model transformation is expected to return a valid target model (forward validity). However, in current model transformation definition and tool support, such an integration with source and target constraints including validation mechanisms is often ignored or not satisfactory yet. In this paper, we describe how the integration with source and target constraints can be achieved for the special case of model transformations defined by Triple Graph Grammars (TGGs). First, we extend the relational model transformation definition for TGGs and integrate it with source and target constraints. Moreover, we describe how forward/backward validity of TGGs with constraints can be automatically checked, either by static analysis using an invariant checker, or by generating and validating metamodel instances. Finally, we describe how to integrate constraints into our TGG-based model transformation implementation and automatic conformance testing framework.

Nucleic acid G-quadruplex structure (G4) Interacting Proteins DataBase (G4IPDB) is an important database that contains detailed information about proteins interacting with nucleic acids that forms G-quadruplex structures. G4IPDB is the first database that provides comprehensive information about this interaction at a single platform. This database contains more than 200 entries with details of interaction such as interacting protein name and their synonyms, their UniProt-ID, source organism, target name and its sequences, ∆Tm, binding/dissociation constants, protein gene name, protein FASTA sequence, interacting residue in protein, related PDB entries, interaction ID, graphical view, PMID, author’s name and techniques that were used to detect their interactions. G4IPDB also provides an efficient web-based “G-quadruplex predictor tool” that searches putative G-quadruplex forming sequences simultaneously in both sense and anti-sense strands of the query nucleotide sequence and provides the predicted G score. Studying the interaction between proteins and nucleic acids forming G-quadruplex structures could be of therapeutic significance for various diseases including cancer and neurological disease, therefore, having detail information about their interactions on a single platform would be helpful for the discovery and development of novel therapeutics. G4IPDB can be routinely updated (twice in year) and freely available on http://bsbe.iiti.ac.in/bsbe/ipdb/index.php.

This paper presents the research work carried out at Oxford University on condition monitoring of railway point machines. The developed condition monitoring system includes a variety of sensors for acquiring trackside data related to different parameters. Key events to be logged include time stamping of points operation, opening and closing of case cover associated with a points machine, insertion and removal of a hand-crank, loss of supply current and the passage of a train. The system also has built-in Web functions. This allows a remote operator using Internet Explorer to observe the condition of the point machine at any time, while the acquired data can be downloaded automatically for offline analysis, providing more detailed information on the health condition of the monitored point machine. A short daily condition report message can also be sent to relevant staff via email. At last the experience are reported on the four trackside installed systems.

The consumption of some psychotropic medicines has a negative effect on the fitness to drive. Pharmacists are expected to give useful advice to patients on their participation in traffic. However, almost no information is available on this topic. To assess the effect of training and implementation of new dispensing guidelines with regard to driving-impairing medicines, in two types of dispensing support tools. User acceptance was measured as well as the effect on pharmacists' attitudes & awareness, self-reported behaviour and knowledge. Pharmacists from East Flanders in Belgium. Two intervention groups and a control group participated. The intervention groups followed a training and were provided with a dispensing support tool containing information on the effect of medicines on driving ability, which was either stand-alone (USB stick) or integrated into the daily used software (ViaNova). The three groups filled out a questionnaire prior to and after the intervention period. Answers to a pre/post-questionnaire on attitudes and awareness, self-reported behaviour, knowledge and user acceptance. Many pharmacists were already strongly interested in the topic at the beginning of the study. Positive changes in attitude, self-reported behaviour and knowledge were measured mostly in the group of pharmacists for which the information was integrated in their daily used software. These pharmacists asked significantly more about the patients' driving experience, informed them more about driving-related risk and gave more detailed information on impairing effects of medicines. The knowledge of the participating pharmacists on the topic 'medicines and driving' remained generally low. The participants acknowledge the importance of being aware of the topic medicines and driving but they report a lack of information or education. They strongly prefer a tool that integrates the information in their daily used software. Dispensing support tools with information on the potential impairing effect of a medicine on the fitness to drive increases awareness, reported risk communication behaviour as well as knowledge of pharmacists on this topic. Computerised dispensing support tools are most effective when the information is integrated into the daily used dispensing software.