Visual Basic wizard Bruce McKinney shows how to blast through the so-called limits of Visual Basic to reach the powerful object-oriented development tool that lurks within. The result is applications with better performance and more functionality. Hardcore Visual Basic provides developers with the coding techniques and finesse to take control of Windows - calling the Windows API, understanding C in Basic, and mastering messages and processes; program objects, Basic style - classes and objects, the form class, collecting objects, and creating new controls by delegating to classes; paint pictures - the Basic way of drawing, painting, and animating; create reusable code - modular packages for sorting, shuffling, searching, and parsing; reusable search, replace, about, and color select forms; classes for editing, animating, managing the keyboard, handling menus, and sharing memory between programs; write portable code - port old 16-bit programs to the 32-bit environment; write new programs that port easily; and push the limits of 32-bit code - break the barriers in Visual Basic to exploit Windows 95 to the fullest. If you want to push Visual Basic to the max, Hardcore Visual Basic is your guide - it's essential for any serious Visual Basic programmer's library.

    The central focus of this book is on the theory of map projections. Mathematical cartography also takes in map scales and their variation, the division of maps into sets of sheets and nomenclature, and addresses the problems of making measurements and conducting investigations which make use of geodetic measurements and the development of graphical methods for solving problems of spherical trigonometry, marine- and aeronavigation, astronomy and even crystallography.

    Enough Rope to Shoot Yourself in the Foot offers well over 100 rules of thumb you can use to create elegant, maintainable code. And since it comes from an acknowledged expert in the field, you can't go wrong. Allen Holub provides an indispensable set of guidelines, tips, and techniques to help you use these extremely powerful languages to the fullest potential. But don't expect another dry programming guide. Holub manages to make a serious subject refreshingly readable by sprinkling the text with humor and insight.

    A reactive system is a system that maintains an ongoing interaction with its environment, as opposed to computing some final value on termination. The family of reactive systems includes many classes of programs whose correct and reliable construction is con- sidered to be particularly challenging, including concurrent programs, embedded and process control programs, and operating systems. Typical examples of such systems are an air traffic control system, programs controlling mechanical devices such as a train, or perpetually ongoing processes such as a nuclear reactor. With the expanding use of computers in safety-critical areas, where failure is potentially disastrous, correctness is crucial. This has led to the introduction of formal verification techniques, which give both users and designers of software and hardware systems greater confidence that the systems they build meet the desired specifications. Framework The approach promoted in this book is based on the use of temporal logic for specifying properties of reactive systems, and develops an extensive verification methodology for proving that a system meets its temporal specification. Reactive programs must be specified in terms of their ongoing behavior, and temporal logic provides an expressive and natural language for specifying this behavior. Our framework for specifying and verifying temporal properties of reactive systems is based on the following four components: 1. A computational model to describe the behavior of reactive systems. The model adopted in this book is that of a Fair Transition System (FTS).

    This means, all too often, that the software you want was written for a slightly different system and that it has to be ported. Despite the best efforts of standards committees and the admirable people who write the software (often giving it away for free), something is likely to go wrong when you try to compile their source code. But help is now here!Problems can crop up at any stage in porting. Special configuration is often required before you compile. The source code could call functions that you've never heard of. Some programs make assumptions about the hardware they're running on or the terminals they interact with. And you may even have trouble with the documentation, if it's in a format you're not used to.This book deals with the whole life cycle of porting, from setting up a source tree on your system to correcting platform differences and even testing the executable after it's built. The book exhaustively discusses the differences between versions of UNIX and the areas where porters tend to have problems.The assumption made in this book is that you just want to get a package working on your system; you don't want to become an expert in the details of your hardware or operating system (much less an expert in the system used by the person who wrote the package!). Many problems can be solved without a knowledge of C or UNIX, while the ones that force you to deal directly with source code are explained as simply and concretely as possible.Topics covered in this book include:Unpacking the softwareCommon configuration tasksIncompatibilities in makefiles and compilersBuilding documentationVariations in system calls, file systems, terminal handling, and other kernel featuresCommonly used librariesCompiler and assembler files

    The CMM is written in abstract terms in order to apply to the most general cases of software practice. The Guide makes the CMM much more accessible to those who wish to understand and study its concepts. The Guide's unique, informal pictograms and clear discussions help you synthesize over 350 pages of the CMM's complex material on 316 software practices.

    This interactive and easy-to-read book also includes many practical examples readers will readily recognize.

    This text aims to help readers learn the software in the context of solving physics problems. The graphical capabilities of Mathematica are emphasized and the readers are encouraged to use their intuition for the physics behind the problem.

    He proposes a humancentric framework in relation to electronic goods, with the superdistribution approach detailed.

    The new edition includes 29 new strategies, including: using feature milestones to deliver results more quickly; extracting useful content from data models; using patterns to discover new features, separating definition from usage; when to use -- or not use -- inheritance; how to decide whether you need an attribute or something more; and why you should nearly always ask for more than a data value.

    An accompanying CD-ROM includes a collection of VRML objects, VRML converter and object-viewing software.

    This text on object-oriented software architecture covers the three qualities of software engineering which are seen as crucial to attain the elusive productivity boost: seamlessness, reversibility, and software contracting.

    It emphasizes abstract data types and their implementation in C++ classes and presents object-oriented programming constructs from C++ to develop the data structures.