DOCSLIB.ORG

Tclpro™ User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Tclpro™ User's Guide TclPro™ User’s Guide • • • • • • Scriptics Corporation Version 1.2 • • • • i • • COPYRIGHT Copyright © 1998, 1999 Scriptics Corporation. All rights reserved. Information in this document is subject to change without notice. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or be any means electronic or mechanical, including but not limited to photocopying and recorded for any purpose other than the purchaser’s personal use, without the express written permission of the Scriptics Corporation. Scriptics Corporation 2593 Coast Avenue Second Floor Mountain View, CA 94043 U.S.A http://www.scriptics.com TRADEMARKS TclPro and Scriptics are trademarks of the Scriptics Corporation. Other products and company names not owned by the Scriptics Corporation that appear in this manual may be trademarks of their respective owners. ACKNOWLEDGEMENTS Michael McLennan is the primary developer of [incr Tcl] and [incr Tk]. Jim Ingham and Lee Bernhard handled the Macintosh and Windows ports of [incr Tcl] and [incr Tk]. Mark Ulferts is the primary developer of [incr Widgets], with other contributions from Sue Yockey, John Sigler, Bill Scott, Alfredo Jahn, Bret Schuhmacher, Tako Schotanus, and Kris Raney. Mark Diekhans and Karl Lehenbauer are the primary developers of Extended Tcl (TclX). Don Libes is the primary developer of Expect. TclPro Wrapper incorporates compression code from the Info-ZIP group. There are no extra charges or costs in TclPro due to the use of this code, and the original compression sources are freely available from http://www.cdrom.com/pub/infozip or ftp://ftp.cdrom.com/pub/infozip. NOTE: TclPro is packaged on this CD using Info-ZIP’s compression utility. The installation program uses UnZip to read zip files from the CD. Info-ZIP’s software (Zip, UnZip, and related utilities) is free and can be obtained as source code or executables from Internet WWW sites including http://www.cdrom.com/pub/infozip. • • • ii • • • Contents • • • • • • Chapter 1 Introduction to TclPro . 1 Installing TclPro . 2 Installing TclPro from CD . 2 Installing TclPro from the Web . 2 Installing Adobe Acrobat Reader . 2 Entering TclPro License Information . 3 About the TclPro Documentation . 4 For More Information . 4 TclPro Technical Support. 5 Finding Information about Tcl/Tk on the Web. 5 Tcl/Tk Training. 5 Related Documentation . 5 Chapter 2 TclPro Interpreters and Extensions . 7 TclPro Interpreters . 7 Running the TclPro Interpreters on Unix . 7 Running the TclPro Interpreters on Windows . 8 Extensions Bundled with TclPro. 8 [incr Tcl] . 8 Expect . 9 Extended Tcl (TclX). 9 Chapter 3 TclPro Debugger. 11 Overview of TclPro Debugger . 11 Supported Tcl Versions . 11 Starting TclPro Debugger. 12 The TclPro Debugger Main Window . 12 The Tool Bar . 14 • • • • iii • • The Stack Display. 14 The Variable Display . 15 The Code Display . 16 The Result Display . 17 Managing Projects. 17 Creating a New Project . 17 Opening an Existing Project . 19 Saving a Project . 20 Closing a Project . 20 Changing Project Settings. 20 Changing Project Application Settings. 20 Changing Project Instrumentation Settings . 23 Changing Project Error Settings . 25 Setting Default Project Settings . 26 Opening a File . 28 Controlling your Application . 28 Running Code with TclPro Debugger. 28 Run to Cursor . 29 Stepping through Code . 29 Stepping In . 29 Stepping Out . 30 Stepping Over . 31 Stepping to Result. 31 Interrupting the Application . 32 Killing the Application . 32 Restarting the Application . 32 Quitting TclPro Debugger. 32 Using Breakpoints . 33 Line-based breakpoints . 33 Variable Breakpoints. 33 Manipulating Breakpoints. 33 Viewing Breakpoints in the Breakpoints Window . 34 Navigating Code . 36 Going to a Specified Line . 36 Using the Find Utility . 36 Finding Procedures . 37 Using the Window Menu . 38 Displaying Code and Data. 38 • • • iv • • • Watching Variables . 38 Displaying Data . 40 Manipulating Data. 41 Error handling . 42 Parsing Error Handling. 42 Runtime Error Handling . 43 Setting Preferences . 44 Appearance Preferences . 45 Window Preferences. 46 Startup and Exit Preferences. 47 Browser Preferences . 48 About TclPro Instrumentation . 49 Debugging Remote, Embedded, and CGI Applications . 50 Modifying a Tcl Script for Remote Debugging . 50 Remote Debugging Procedures . 50 Creating a “Wrapper” Script for Remote Debugging . 51 Modifying an Existing Script for Remote Debugging . ..
Load more

Recommended publications
  • Ajuba Solutions Version 1.4 COPYRIGHT Copyright © 1998-2000 Ajuba Solutions Inc
    • • • • • • Ajuba Solutions Version 1.4 COPYRIGHT Copyright © 1998-2000 Ajuba Solutions Inc. All rights reserved. Information in this document is subject to change without notice. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means electronic or mechanical, including but not limited to photocopying or recording, for any purpose other than the purchaser’s personal use, without the express written permission of Ajuba Solutions Inc. Ajuba Solutions Inc. 2593 Coast Avenue Mountain View, CA 94043 U.S.A http://www.ajubasolutions.com TRADEMARKS TclPro and Ajuba Solutions are trademarks of Ajuba Solutions Inc. Other products and company names not owned by Ajuba Solutions Inc. that appear in this manual may be trademarks of their respective owners. ACKNOWLEDGEMENTS Michael McLennan is the primary developer of [incr Tcl] and [incr Tk]. Jim Ingham and Lee Bernhard handled the Macintosh and Windows ports of [incr Tcl] and [incr Tk]. Mark Ulferts is the primary developer of [incr Widgets], with other contributions from Sue Yockey, John Sigler, Bill Scott, Alfredo Jahn, Bret Schuhmacher, Tako Schotanus, and Kris Raney. Mark Diekhans and Karl Lehenbauer are the primary developers of Extended Tcl (TclX). Don Libes is the primary developer of Expect. TclPro Wrapper incorporates compression code from the Info-ZIP group. There are no extra charges or costs in TclPro due to the use of this code, and the original compression sources are freely available from http://www.cdrom.com/pub/infozip or ftp://ftp.cdrom.com/pub/infozip. NOTE: TclPro is packaged on this CD using Info-ZIP’s compression utility.
    [Show full text]
  • Scripting: Higher- Level Programming for the 21St Century
    . John K. Ousterhout Sun Microsystems Laboratories Scripting: Higher- Cybersquare Level Programming for the 21st Century Increases in computer speed and changes in the application mix are making scripting languages more and more important for the applications of the future. Scripting languages differ from system programming languages in that they are designed for “gluing” applications together. They use typeless approaches to achieve a higher level of programming and more rapid application development than system programming languages. or the past 15 years, a fundamental change has been ated with system programming languages and glued Foccurring in the way people write computer programs. together with scripting languages. However, several The change is a transition from system programming recent trends, such as faster machines, better script- languages such as C or C++ to scripting languages such ing languages, the increasing importance of graphical as Perl or Tcl. Although many people are participat- user interfaces (GUIs) and component architectures, ing in the change, few realize that the change is occur- and the growth of the Internet, have greatly expanded ring and even fewer know why it is happening. This the applicability of scripting languages. These trends article explains why scripting languages will handle will continue over the next decade, with more and many of the programming tasks in the next century more new applications written entirely in scripting better than system programming languages. languages and system programming
    [Show full text]
  • Ixia Tcl Development Guide
    Chapter 2: Quick Start 2 Installing the IxOS Tcl Client This chapter provides a quick means of getting started with the Tcl API. An example test is presented and explained. The IxOS Tcl Client provides an interface between an Ixia Tcl client application and Ixia IxOS Tcl functions. It runs on the Unix / Linux host. The Windows version of IxOS Tcl Client is included with the IxOS software package; the Unix/Linux version is supplied as a separate a self-extracting archive (.bin) file. You can download it from Ixia’s website, www.ixiacom.com. There are serveral versions of the IxOS Tcl Client. The correct file to install depends on the set up of the UNIX/Linux machine. Table 2-2 on page 2-1 details the files and their use. Table 2-2. Tcl Client Install Files Install File Purpose IxOS#.## For Linux versions post Redhat 9. It is distributed as genericLinux.bin a tarball (IxOS#.##genericLinux.bin.tar.gz) due to download issues. IxOS#.##linux.bin. For Linux platforms older than Redhat 9. IxOS#.##setup.jar An installer without a bundled Java Virtual Machine. This is distributed only to customers that have issues running the bin installers. It requires a Java Virtual Machine installed on the installation target. IxOS#.## For Solaris machines. solarisSparc.bin The versions of UNIX/Linux operating systems that are supported are: • Mandrake 7.2, RedHat 6.2, RedHat 7.0, RedHat 9.0 • RedHat Enterprise 4.0 IxOS Tcl Development Guide, 6.60 EA SP1 2-1 Quick Start 2 Installing the IxOS Tcl Client • Solaris 2.7 (7), 2.8 (8), 2.9 (9) Other versions of Linux and Solaris platforms may operate properly, but are not officially supported.
    [Show full text]
  • Automating Your Sync Testing
    APPLICATION NOTE By automating system verification and conformance testing to ITU-T synchronization standards, you’ll save on time and resources, and avoid potential test execution errors. This application note describes how you can use the Paragon-X’s Script Recorder to easily record Tcl, PERL and Python commands that can be integrated into your own test scripts for fast and efficient automated testing. AUTOMATING YOUR SYNC TESTING calnexsol.com Easily automate synchronization testing using the Paragon-X Fast and easy automation by Supports the key test languages Pre-prepared G.8262 Conformance recording GUI key presses Tcl, PERL and Python Scripts reduces test execution errors <Tcl> <PERL> <python> If you perform System Verification language you want to record i.e. Tcl, PERL SyncE CONFORMANCE TEST and Conformance Testing to ITU-T or Python, then select Start. synchronization standards on a regular Calnex provides Conformance Test Scripts basis, you’ll know that manual operation to ITU-T G.8262 for SyncE conformance of these tests can be time consuming, testing using the Paragon-X. These tedious and prone to operator error — as test scripts can also be easily tailored well as tying up much needed resources. and edited to meet your exact test Automation is the answer but very often requirements. This provides an easy means a lack of time and resource means it of getting your test automation up and remains on the ‘To do’ list. Now, with running and providing a repeatable means Calnex’s new Script Recorder feature, you of proving performance, primarily for ITU-T can get your automation up and running standards conformance.
    [Show full text]
  • Dwarf's Guide to Debian GNU/Linux
    Dwarf’s Guide to Debian GNU/Linux 2001 Dale Scheetz Dwarf’s Guide to Debian GNU/Linux Copyright c 2001 Dale Scheetz Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being Chapter 1 Introduction, with no Front-Cover Texts, and with the Back-Cover Texts being “The early development of the material in this work was produced with the financial support of Planet Linux. This support was intrumental in bringing this project to completion.” A copy of the license is included in the section entitled “Appendix 9: GNU Free Documentation License” which can be found on page 271. Trademark Acknowledgements All terms mentioned in this book that are known to be trademarks or service marks have been appropriately capitalized. The publisher cannot attest to the accuracy of this information. Use of a term in this book should not be regarded as affecting the validity of any trademark or service mark. Apple and Macintosh are registered trademarks of Apple Computer, Inc. CP/M is a registered trademark of Caldera, Inc. IBM is a registered trademark of International Business Machines, Inc. MS is a trademark of Microsoft Corporation. Windows is a trademark of Microsoft Corporation. X Window System is a registered trademark of X Consortium, Inc. ii dedicated to Linux users everywhere iii CREDITS First I want to thank Ian Murdock for writing the History section. His per- spectives on those early years have helped latecomers like Dwarf understand the founding principles upon which Debian is based.
    [Show full text]
  • PIC Licensing Information User Manual
    Oracle® Communications Performance Intelligence Center Licensing Information User Manual Release 10.1 E56971 Revision 3 April 2015 Oracle Communications Performance Intelligence Center Licensing Information User Manual, Release 10.1 Copyright © 2003, 2015 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notices are applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • 13A04806 LINUX PROGRAMMING and SCRIPTING UNIT 4 TCL/ TK SCRIPTING:Tcl Fundamentals, String and Pattern Matching, Tcl Data Struct
    13A04806 LINUX PROGRAMMING AND SCRIPTING UNIT 4 TCL/ TK SCRIPTING:Tcl Fundamentals, String and Pattern Matching, Tcl Data Structures ,Control Flow Commands, Procedures and Scope , Evel, Working With UNIX, Reflection and Debugging, Script Libraries, Tk Fundamentals ,Tk by Examples, The Pack Geometry Manager, Binding Commands to X Events, Buttons and Menus, Simple Tk Widgets, Entry and Listbox Widgets Focus, Grabs and Dialogs 13A04806 LINUX PROGRAMMING AND SCRIPTING Tcl - Overview Tcl is shortened form of Tool Command Language. John Ousterhout of the University of California, Berkeley, designed it. It is a combination of a scripting language and its own interpreter that gets embedded to the application, we develop with it. Tcl was developed initially for Unix. It was then ported to Windows, DOS, OS/2, and Mac OSX. Tcl is much similar to other unix shell languages like Bourne Shell (Sh), the C Shell (csh), the Korn Shell (sh), and Perl. It aims at providing ability for programs to interact with other programs and also for acting as an embeddable interpreter. Even though, the original aim was to enable programs to interact, you can find full-fledged applications written in Tcl/Tk. Features of Tcl The features of Tcl are as follows − ∑ Reduced development time. ∑ Powerful and simple user interface kit with integration of TK. ∑ Write once, run anywhere. It runs on Windows, Mac OS X, and almost on every Unix platform. ∑ Quite easy to get started for experienced programmers; since, the language is so simple that they can learn Tcl in a few hours or days. ∑ You can easily extend existing applications with Tcl.
    [Show full text]
  • Advanced Tcl E D
    PART II I I . A d v a n c Advanced Tcl e d T c l Part II describes advanced programming techniques that support sophisticated applications. The Tcl interfaces remain simple, so you can quickly construct pow- erful applications. Chapter 10 describes eval, which lets you create Tcl programs on the fly. There are tricks with using eval correctly, and a few rules of thumb to make your life easier. Chapter 11 describes regular expressions. This is the most powerful string processing facility in Tcl. This chapter includes a cookbook of useful regular expressions. Chapter 12 describes the library and package facility used to organize your code into reusable modules. Chapter 13 describes introspection and debugging. Introspection provides information about the state of the Tcl interpreter. Chapter 14 describes namespaces that partition the global scope for vari- ables and procedures. Namespaces help you structure large Tcl applications. Chapter 15 describes the features that support Internationalization, includ- ing Unicode, other character set encodings, and message catalogs. Chapter 16 describes event-driven I/O programming. This lets you run pro- cess pipelines in the background. It is also very useful with network socket pro- gramming, which is the topic of Chapter 17. Chapter 18 describes TclHttpd, a Web server built entirely in Tcl. You can build applications on top of TclHttpd, or integrate the server into existing appli- cations to give them a web interface. TclHttpd also supports regular Web sites. Chapter 19 describes Safe-Tcl and using multiple Tcl interpreters. You can create multiple Tcl interpreters for your application. If an interpreter is safe, then you can grant it restricted functionality.
    [Show full text]
  • 7 Reasons the Future of Tcl Is Bright by Clif Flynt ([email protected]) 7 Reasons the Future of Tcl Is Bright
    7 REASONS THE FUTURE OF TCL IS BRIGHT BY CLIF FLYNT ([email protected]) 7 REASONS THE FUTURE OF TCL IS BRIGHT The future is bright for Tcl! You’d be pardoned for his repertoire. He started shell programming in 1985, thinking otherwise. It’s not a sexy new language. In fact, picked up Perl in 1995 and finally Tcl in 1996. He’s been a it’s ranked outside the Top 50 in the TIOBE Index1. Tcl devotee ever since. But for the right projects - and there are lots of them - it’s With Clif’s extensive background, we asked him about a powerful tool that’s been stress-tested for many years the future of Tcl. Here’s seven reasons why the future and just gets the job done. of Tcl is bright. Tcl is not resting on its laurels. The simplicity of the Tcl language makes it perfect for Internet of Things IoT and 1: TCL IS STILL THE KING OF electronics design, including Electronic Design Automa- RAPID PROTOTYPING tion (EDA), chip design, and Field-Programmable Gate Clif is a big fan of Tcl for rapid prototypes that actually Array (FPGA) development, and for configuring chips after work. NBC Broadcasting studios uses Tcl/Tk to control manufacture. The same features that make Tcl dominant what you see. They went to GE Research (and others) in EDA and FPGA also make it great for DevOps, poten- with a half-baked design and some examples of the tially competing with Bash and Perl as the language of clipboards and tapes they were using.
    [Show full text]
  • Fast Integration of EDA Tools and Scripting Language
    Fast Integration of EDA Tools and Scripting Language Dept. of EECS, U. C. Berkeley Berkeley, CA 94720, USA [email protected] Abstract such as Skill for Silicon Ensemble[6], Scheme for Apollo II[7], or Tcl[2] for Design Compiler[8]. However, a specific programming EDA tools are implemented to automate a design task efficiently, language may be another stopping factor for a user to further ex- but they often lack flexibility to be highly customizable or pro- plore the tool, just because a long learning curve is required for a grammable. Some EDA tools have a primitive and unique com- new programming language. For modern chip design, a designer mand language to realize programmability, but usually it further has to deal with at least a dozen of tools, each of which may have a complicates a design flow. We thus propose methods and crucial unique command language plus several specific input formats. This techniques to fast link EDA tools with a popular scripting language could be a very error-prone process and impede design productivity such as Perl[1], Tcl[2] or Python[3] for ease-of-use and better inte- seriously. gration. This approach encourages rapid prototyping of algorithms, Perl and Tcl have been extensively used in the design commu- code reuse, customizability, extensibility, interoperability between nity for a long time due to their powerful string pattern match by tools, and easier testing of application program interface(API)’s. regular expressions, scripting capability, popularity, and extensibil- Based on the proposed methods and techniques, we efficiently ity. Both can process a simple text file very efficiently using regular built several Perl/Tcl/Python interfaces to EDA packages such as expressions without the tedium to program a full parser and a lexi- LEF/DEF parser, Synopsys .lib parser, Verilog PLI2.0 routines, cal analyzer.
    [Show full text]
  • Embedding an Interpreted Language Using Higher-Order Functions and Types
    JFP 17 1–000, January 2008. c 2008 Cambridge University Press 1 DOI: 10.1017/S0000000000000000 Printed in the United Kingdom Embedding an Interpreted Language Using Higher-Order Functions and Types Norman Ramsey Department of Computer Science Tufts University Abstract Using an embedded, interpreted language to control a complicated application can have significant software-engineering benefits. But existing interpreters are designed for embedding into C code. To embed an interpreter into a different language requires an API suited to that language. This paper presents Lua-ML, a new API that is suited to languages that provide higher-order functions and types. The API exploits higher-order functions and types to reduce the amount of glue code needed to use an embedded interpreter. Where embedding in C requires a special-purpose “glue function” for every function to be embedded, embedding in Lua-ML requires only a description of each function’s type. Lua-ML also makes it easy to define a Lua function whose behavior depends on the number and types of its arguments. 1 Introduction Suppose you have an application written in a statically typed, compiled language such as C, C++, or ML. If the application is complicated, like a web server or an optimizing compiler, it will have lots of potential configurations and behaviors. How are you to control it? If you use command-line arguments, you may find yourself writing an interpreter for an increasingly complicated language of command-line arguments. If you use a configuration file, you will find yourself defining, parsing, and interpreting its syntax. A better idea, which we owe to Ousterhout (1990), is to create a reusable language de- signed just for configuring and controlling application programs, i.e., for scripting.
    [Show full text]
  • Linux Installation and Getting Started
    Linux Installation and Getting Started Copyright c 1992–1996 Matt Welsh Version 2.3, 22 February 1996. This book is an installation and new-user guide for the Linux system, meant for UNIX novices and gurus alike. Contained herein is information on how to obtain Linux, installation of the software, a beginning tutorial for new UNIX users, and an introduction to system administration. It is meant to be general enough to be applicable to any distribution of the Linux software. This book is freely distributable; you may copy and redistribute it under certain conditions. Please see the copyright and distribution statement on page xiii. Contents Preface ix Audience ............................................... ix Organization.............................................. x Acknowledgments . x CreditsandLegalese ......................................... xii Documentation Conventions . xiv 1 Introduction to Linux 1 1.1 About This Book ........................................ 1 1.2 A Brief History of Linux .................................... 2 1.3 System Features ......................................... 4 1.4 Software Features ........................................ 5 1.4.1 Basic commands and utilities ............................. 6 1.4.2 Text processing and word processing ......................... 7 1.4.3 Programming languages and utilities .......................... 9 1.4.4 The X Window System ................................. 10 1.4.5 Networking ....................................... 11 1.4.6 Telecommunications and BBS software .......................
    [Show full text]