Balachander Krishnamurthy, editor. Practical reusable UNIX software. John Wiley & Sons, Inc., 1995.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....work in large, practical settings, yet provides fine grained control where such coarse mechanisms are insufficient. Other crucial differences are outlined in Section 6. Per process name spaces have previously been implemented as shared libraries (e.g. union directories and versioning in n DFS ( Kri95, Section 2.5] We chose not to rely on the use of shared libraries because it may be undesirable to force processes to unconditionally link with a specified library. 6 Advantages Provided by the Supernet Abstraction 6.1 Independent Addressing A key consequence of the Supernet abstraction is an ....

Balachander Krishnamurthy, editor. Practical Reusable UNIX Software. John Wiley, 1995.

.... reading; Kernighan [12] reflects on the troff family; this author has described the design and implementation of Lout [13] But for the most part one has to infer principles from the systems themselves, and to look among the specialized applications such as music formatting [5] graph drawing [11, 23, 17], or non European languages for requirements. This paper draws on its author s twelve years of experience in designing, implementing,and enhancing the Lout document formatting system, plus his more limited experience of the systems mentioned above, to identify a set of requirements for a document ....

....may display a parameter more than once, in which case editing one display must change them all. Preserving editability of displayed parameters is a difficult problem when the function is implemented externally to the document editing system. For example, if an external graph layout program [17] is employed, the result cannot be returned as a bitmap or PostScript file; rather a set of coordinate pairs or something similar is required so that the document formatter can place the nodes itself and hence understand where they ended up. It has been suggested that a non editable result is ....

Balachander Krishnamurthy (ed.). Practical Reusable UNIX Software. John Wiley, 1995.

....Alternatively, a collection of tools could be bundled as hypertools, where separate programs run simultaneously and communicate with each other. This hypertool concept is in keeping with the philosophy of allowing independent tools cooperate as seen in program environments like Field [7] and Yeast [5]. Field integrated a wide variety of Unix tools using a message based integration mechanism. Yeast widened the domain to include all eventaction applications. Since these techniques make use of existing tools and mechanisms, an updated tool would require little or no change to the environment. ....

Balachander Krishnamurthy. Practical Reusable UNIX Software. John Wiley and sons, New York, NY, 1995.

....graphs are perhaps the most common method for showing the relationships among software entities. They are the foundation of many CASE and program analysis tools. For example, a node in the graph may represent a procedure and an edge may represent a calling relationship between two procedures [Kri95]. Run time behavior. Algorithm animation uses graphical representations of data structures and motion to illustrate the higher level behavior of algorithms [Bro88] Lower level views based on program profiles or traces can reveal bugs and performance anomalies [CBEL95] The code itself. Pretty ....

....These graphs, found in virtually all CASE tools, usually consist of node and link diagrams carefully arranged by sophisticated layout algorithms to show the underlying structure of complicated systems. The graphs may describe relationships such as procedure or function calls or class inheritance [Kri95]. The function call graphs may be animated as a visual representation of how a program executes and color coded to show hot spots, parts of the system using excessive amounts of CPU time that may be candidates for optimization. Perhaps the most difficult aspect of showing software through graphs ....

Balachander Krishnamurthy, editor. Practical Reusable UNIX Software. John Wiley & Sons, Inc., New York, New York, 1995.

....Since these are functional objects, the site of connection can make a significant functional difference. No currently available graph browsers are able to support the idea of connection sites, or Pins. As a result, all incoming connections are attached to a single point of entry to the node. DOT[15, 14, 6] does contain a limited facility for connecting to different physical sites on a node, but it is not sufficiently flexible. Moorman and Millman s[22, 21] Mustang tool uses an automatically generated static layout, and graphically displays information about testability (controllability and ....

....drawing. This approach, while vastly scalable, made it impossible to use a real functional layout as a basis for connection data. It does provide the user with the ability to interactively trace connections, but it can not display any information beyond this connection information. AT T s LEFTY [14, 15] is used as a front end to DOT, and it provides sophisticated language extensions. However, it is not possible to extract information from LEFTY for re layout. Also, LEFTY does not provide any interactive database. It would be possible to write an external tool for LEFTY that could use LEFTY as a ....

Balachander Krishnamurthy. practical Reusable UNIX software. John Wiley & Sons, INC., 1995.

....These graphs, found in virtually all CASE tools, usually consist of node and link diagrams carefully arranged by sophisticated layout algorithms to show the underlying structure of complicated systems. The graphs may describe relationships such as procedure or function calls or class inheritance [Kri95]. The function call graphs may be animated as a visual representation of how a program executes and color coded to show hot spots, parts of the system using excessive amounts of CPU time that may be candidates for optimization. Perhaps the most difficult aspect of showing software through graphs ....

Balachander Krishnamurthy, editor. Practical Reusable UNIX Software. John Wiley & Sons, Inc., New York, New York, 1995.

No context found.

Balachander Krishnamurthy, editor. Practical reusable UNIX software. John Wiley & Sons, Inc., 1995.

No context found.

Balachander Krishnamurthy. Practical reusable unix software, 1995.

No context found.

Balachander Krishnamurthy, Practical Reusable UNIX Software, John Wiley Sons, Inc., 1995.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC