The Structure and Semantics of an Object-Oriented Logic Programming Language: SCKE

The development of the object-oriented paradigm has suffered from the lack of any generally accepted formal foundations for its semantic definition.To address this issue,we propose the development of the logic-based semantics of the object-oriented paradigm.By combining the logic-with the object-oriented paradigm of computing first,this paper discusses formally the semantics of a quite purely object-oriented logic paradigm in terms of proof theory,model theory and fixpoint theory from the viewpoint of logic.The operational and declarative semantics is given.And then the correspondence between soundness and completeness has been discussed formally.     

Java编程语言在大数据开发中的应用探究

文章首先分析Java编程语言系统概论﹐并且结合Java编程语言系统的特点以及Java编程语言系统现状,进一步总结了Java编程语言系统应用策略。     

The BLAZE language: A parallel language for scientific programming

Programming multiprocessor parallel architectures is a complex task. This paper describes a block-structured scientific programming language, BLAZE, designed to simplify this task. BLAZE contains array arithmetic, ‘forall’ loops, and APL-style accumulation operators, which allow natural expression of fine grained parallelism. It also employs an applicative or functional procedure invocation mechanism, which makes it easy for compilers to extract coarse grained parallelism using machine specific program restructuring. Thus BLAZE should allow one to achieve highly parallel execution on multiprocessor architectures, while still providing the user with conceptually sequential control flow.

A central goal in the design of BLAZE is portability across a broad range of parallel architectures. The multiple levels of parallelism present in BLAZE code, in principle, allow a compiler to extract the types of parallelism appropriate for the given architecture, while neglecting the remainder. This paper describes the features of BLAZE, and show how this language would be used in typical scientific programming.     

The BLISS programming language: a history

The BLISS programming language was invented by William A. Wulf and others at Carnegie‐Mellon University in 1969, originally for the DEC PDP‐10. BLISS‐10 caught the interest of Ronald F. Brender of DEC (Digital Equipment Corporation). After several years of collaboration, including the creation of BLISS‐11 for the PDP‐11, BLISS was adopted as DEC's implementation language for use on its new line of VAX computers in 1975. DEC developed a completely new generation of BLISSs for the VAX, PDP‐10 and PDP‐11, which became widely used at DEC during the 1970s and 1980s. With the creation of the Alpha architecture in the early 1990s, BLISS was extended again, in both 32‐ and 64‐bit flavors. BLISS support for the Intel IA‐32 architecture was introduced in 1995 and IA‐64 support is now in progress. BLISS has a number of unusual characteristics: it is typeless, requires use of an explicit contents of operator (written as a period or ‘dot’), takes an algorithmic approach to data structure definition, has no goto , is an expression language, and has an unusually rich compile‐time language. This paper reviews the evolution and use of BLISS over its three decade lifetime. Emphasis is on how the language evolved to facilitate portable programming while retaining its initial highly machine‐specific character. Finally, the success of its characteristics are assessed. Copyright © 2002 John Wiley & Sons, Ltd.     

Studying the language and structure in non-programmers' solutions to programming problems

Programming may be more difficult than necessary because it requires solutions to be expressed in ways that are not familiar or natural for beginners. To identify what is natural, this article examines the ways that non-programmers express solutions to problems that were chosen to be representative of common programming tasks. The vocabulary and structure in these solutions is compared with the vocabulary and structure in modern programming languages, to identify the features and paradigms that seem to match these natural tendencies as well as those that do not. This information can be used by the designers of future programming languages to guide the selection and generation of language features. This design technique can result in languages that are easier to learn and use, because the languages will better match beginners' existing problem-solving abilities.     

The effects of feedback on performance and retention of skill for a natural language interface

This study investigated the effectiveness of different types of on-line feedback following user errors for informing users of the information and functions available in a system with a natural language interface. Twenty-four individuals performed a task based on an industry cost savings program, in which they were given general goals to pursue with regard to the task. Three feedback levels which differed according to the type and amount of feedback provided, along with two levels of system complexity, were examined. In addition, subjects performed the task again after one week to determine the effects of feedback on retention. Results indicated that the subjects in the second level of feedback generally performed better with respect to accessing system functions and information than those in the first level. Although there was some performance improvement from the second to third level, it was not significant. However, the third level of feedback did significantly improve the efficiency with which subjects used information to complete the task during the return condition. Overall, feedback did not affect the errors made, though at certain more limited stages of the tasks this effect was observed.     

The C programming language: Popularity grows for the high-level assembly language

The programming language C is becoming increasingly popular. It has many advantages over PASCAL and BASIC for use with PCs. It is known as a high-level assembly language, and provides useful tools for programmers.     

The training effects of principle knowledge on fault diagnosis performance

In regard to the effectiveness of types of knowledge on fault diagnosis performance, many experimental studies showed that training with procedural knowledge (diagnostic rules) is very effective to enhance diagnosis performance. But the effects of training with principle knowledge (theoretical knowledge) have been controversial. Some studies went so far as to claim that principle knowledge is not useful for diagnosis. However, common experience suggests that understanding the principles of system dynamics is valuable in certain diagnostic situations. In this study, we conducted an experiment to investigate the value of principle knowledge in various fault situations. A context‐free digital logic circuit including 41 gates of three basic types was simulated for the subjects to diagnose. The experimental results showed that instructing principle knowledge has positive effects that are dependent on the complexity of diagnostic problems. The observations also provide insights on how fault diagnosis benefits from principle knowledge. © 2007 Wiley Periodicals, Inc. Hum Factors Man 17: 263–282, 2007.     

面向职业技能培养的软件开发课程改革探索

传统的软件开发课程,以培养编程技能和逻辑思维能力为主,已远不能满足人才市场的职业化需求.在分析当前软件开发课程存在问题的基础上,结合C语言程序设计课程教学实践,将信息系统软件运行机理融入课堂教学实践,提出面向职业技能培养的教学改革方案,并给出课堂教学内容设计实际案例.实践证明,该教学方案提高了学生灵活运用知识、解决实际问题的工程能力.     

The current programming language standards scene XIVA: APL

Developments in the standardisation of APL during the period January 1980 to May 1983 are reviewed.     

The current programming language standards scene X: Graphics

Developments in the standardisation of graphics handling in computer systems during the period January 1980 to May 1983 are reviewed.     

The current programming language standards scene VI: BASIC

Developments in the standardisation of BASIC during the period January 1980 to May 1983 are reviewed.     

The current programming language standards scene XII: Metalanguages

Developments in the standisation of the syntactic metalanguages during the period January 1980 to May 1983 are reviewed.     

The current programming language standards scene III: COBOL

Developments in the standardisation of COBOL during the period January 1980 to May 1983 are reviewed.     

The development, validity and reliability of TPACK-deep: A technological pedagogical content knowledge scale

The purpose of this study is to develop a TPACK (technological pedagogical content knowledge) scale based on the centered component of TPACK framework in order to measure preservice teachers’ TPACK. A systematic and step-by-step approach was followed for the development of the scale. The validity and reliability studies of the scale were carried out with 995 Turkish preservice teachers. The sample was split into two subsamples on random basis (n1 = 498, n2 = 497). The first sample was used for Exploratory Factor Analysis (EFA) and the second sample for Confirmatory Factor Analysis (CFA). After the EFA, the TPACK-deep scale included 33 items and had four factors. These factors were design, exertion, ethics and proficiency. The Cronbach’s alpha coefficient for the whole scale was found to be .95, whereas the values of Cronbach’s alpha coefficient for individual factors of the scale ranged between .85 and .92. The CFA was conducted within the scope of the validity study of the scale. In this way, this structure of the 4-factor scale was confirmed. In addition, the test-retest reliability coefficient of the scale was calculated as .80. The findings revealed that the TPACK-deep scale was a valid and reliable instrument for measuring TPACK. Consequently, various suggestions were put forward regarding the use the TPACK-deep scale for applied research and for future studies.     

Visual Basic中窗体界面设计技巧的探讨

在程序设计中,一个好的应用程序(或软件)除了要有强大的功能外,简洁、明了、统一的用户界面也是至关重要的,本文以Vi-sualBasic语言为例,就这一方面的问题进行了论述,并举例说明。     

The design of a portable programming language

Summary We consider the design of a strongly-typed language with userdefined types in which it is arranged that, given that a type is available, it is immaterial to the user whether it is a user-defined type or one of the primitive types with representations selected by the implementer. This scheme provides unprecedented freedom in choosing the primitive types; by making these machine-dependent we can ensure production of programs that are easily and efficiently portable between computers of different architectures. A general discussion of the implementer's responsibilities in choosing primitive types appropriate to his machine is illustrated by considering implementation choices for translation of the language into BCPL. Finally we discuss the contribution of the language to the solution of the portability problem.