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 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.     

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

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

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 XIVA: APL

Developments in the standardisation of APL 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.     

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.     

The consequences of one's first programming language

After seeing many programs written in one language, but with the style and structure of another, I conducted an informal survey to determine whether this phenomenon was widespread and to determine how much a programmer's first programming language might be responsible. This paper discusses my observations, gives informal results of the survey and suggests the need for a more formal study.     

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

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

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

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

An evaluation of programming languages and language features for engineering software development

This article addresses the need for engineers to have a working knowledge of the fundamental structures of computer programming languages. In pursuit of this, it briefly looks at the history behind four of the more well-known programming languages. It then attempts to identify, and to look critically at, the attributes of programming languages that significantly affect the production of engineering software. The four traditional procedural programming languages chosen for review are those intended for scientific and general purpose programmin—FORTRAN-77, C, Pascal, and Modula-2. These languages are compared and some general observations are made.The emphasis of this article is on the attributes, characteristics, and components of programming languages that are important to software development and maintenance. Consequently, the comparison itself is of secondary importance, with the actual methodology of comparison given prominence in order that professional engineers who need to develop engineering software are able to make rational decisions about the choice of a programming language. Choosing an appropriate language can be a complex task and many factors must be considered. Therefore, in this article the fundamental structures, constructs, and attributes of programming languages are discussed, with very little attention given to the specific syntax of any particular language.     

The Lynx distributed programming language: Motivation, design and experience

A programming language can provide much better support for interprocess communication than a library package can. Most message-passing languages limit this support to communication between the pieces of a single program, but this need not be the case. Lynx facilitates convenient, typesafe message passing not only within applications, but also between applications and among distributed collections of servers. Specifically, it addresses issues of compiler statelessness, late binding, and protection that allow run-time interaction between processes that were developed independently and that do not trust each other. Implementation experience with Lynx has yielded important insights into the relationship between distributed operating systems and language run-time support packages and into the inherent costs of high-level message-passing semantics.     

Concurrent programming in the Ada® language: The polling bias

The rendezvous is an important concept in concurrent programming—two processes need to synchronize, i.e. rendezvous, to exchange information. The Ada programming language is the first programming language to use the rendezvous as the basis of its concurrent programming facilities. Our experience with rendezvous facilities in the Ada language shows that these facilities lead to and encourage the design of programs that poll. Polling is generally, but not always, undesirable because it is wasteful of system resources. We illustrate and examine the reasons for polling bias in the Ada language. We give suggestions on how to avoid polling programs, and suggest changes to the rendezvous facilities to eliminate the polling bias. The ramifications of these changes to the implementation of the Ada language are also discussed. Although we have focused on the rendezvous facilities in the Ada language our analysis is also applicable to other languages. A polling bias can occur in any concurrent programming language based on the rendezvous mechanism if it does not provide appropriate facilities.     

The manipulator language with the characteristic of a functional programming language

This article describes the motion-oriented robot language IML (interactive manipulator language) with the characteristic of a functional programming language. The main functions of IML are (1) It is possible to describe the iterative motions without using a loop. (2) The user-defined procedures (commands) can be called by specifying the command name. (3) It is possible to describe robot motion (a sequence of the position and orientation of a robot hand) and force magnitude in the task-oriented Cartesian coordinate system (task coordinate system) suitable for robot tasks. Furthermore, it is possible to describe the translation and rotation of the coordinate system without syntactic distinction. (4) As the teaching data can be easily embedded in the language and can be played back in the force control mode, complex task programming becomes easy. In IML, as the user-defined command and the teaching data can be used just as the builtin system command; the system can be extended easily and naturally. In this article these features are described, and it is shown that these functions can be realized with the unified representation by introducing the concept of a functional programming language. The effectiveness of IML was confirmed by actually making a robot perform some tasks programmed in IML.