Language choice of the Foochows in Sarawak, Malaysia

This paper investigates the factors affecting the language choices of the Chinese Foochows of Sarawak, focusing in particular on how the use of the Foochow dialect vis-a`-vis English and other languages might potentially result in a shift in language allegiance away from Foochow. In the context of Sarawak, the Foochows are a substantial, cohesive and homogeneous Chinese ethnic group with a distinctive language and ethnic identity. One would predict that they would engage in extensive language maintenance behaviour. Instead, Foochows living in non-Foochow dominant areas do not seem to have sufficient attachment to the language to transmit it to the next generation. Is this because the Foochows consider that accommodating to communicative norms is more important than preserving their native language as an inherent symbol of their ethnic identity? Or is it the result of the Foochows’ insecurity about the prestige of the dialect and the status of the Foochow people? These issues of accommodation and language allegiance are discussed, based on interview and questionnaire data from 11 Foochow participants. This data set is part of a larger study on the language use of different ethnic groups in multilingual organisational settings in Sarawak.

API documentation with executable examples

The rise of component-based software development has created an urgent need for effective application program interface (API) documentation. Experience has shown that it is hard to create precise and readable documentation. Prose documentation can provide a good overview but lacks precision. Formal methods offer precision but the resulting documentation is expensive to develop. Worse, few developers have the skill or inclination to read formal documentation. We present a pragmatic solution to the problem of API documentation. We augment the prose documentation with executable test cases, including expected outputs, and use the prose plus the test cases as the documentation. With appropriate tool support, the test cases are easy to develop and read. Such test cases constitute a completely formal, albeit partial, specification of input/output behavior. Equally important, consistency between code and documentation is demonstrated by running the test cases. This approach provides an attractive bridge between formal and informal documentation. We also present a tool that supports compact and readable test cases; and generation of test drivers and documentation, and illustrate the approach with detailed case studies. (C) 2002 Elsevier Science Inc. All rights reserved.