DOCSLIB.ORG

Prashant Thakre and Tushar Gupta

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Prashant Thakre and Tushar Gupta Porting a large scale enterprise application from 2.0 Glossary Tcl/Tk 8.4 to 8.5 - A Case Study Description of terms used in the paper: Prashant Thakre, Tushar Gupta {prashant_thakre, [incr Tcl] - is an OO system for tushar_gupta}@mentor.com Tcl, and [incr Tcl] provides a similar object model, including multiple inheritance, and public 1.0 Abstract and private classes and variables. This paper describes the challenges involved in porting a [incr Tk] - Megawidget large scale enterprise framework based upon [incr application from Tcl/Tk 8.4 to Tcl]. Tcl/Tk 8.5, and lists down all Iwidgtes - is an object-oriented issues encountered during the mega-widget set which extends migration. The migration to Tcl/Tk and is based on [incr Tcl] Tcl/Tk 8.5 required adjustments and [incr Tk]. in application code, necessitated due to changes in [mti Widgets] - Collection of interface, or as a result of mega-widget, additions and unexpected functional enhancements to Iwidgets. This behaviour. On some occasions it megawidget requires TIP #125 was required to patch the (wm toplevel) Tcl/Tk 8.5 distribution with fixes which are now expected to be included into standard Tcl/Tk 3.0 Motivation release. The application Veloce The case-study describes in GUI, is from the Mentor detail various external and Emulation Division (MED) at internal dependencies requiring Mentor Graphics Corp. The resolution and covers Veloce GUI is used for performance related emulation compiles, emulation benchmarks/issues. Also, runtime control, and project changes in various packages management and most (core and external) resulting in importantly for design debug. regressions are discussed. The Typically customers use objective of the case-study is to emulation for some of the provide other developers an in- largest and the most complex sight into typical issues faced, System-on-a-chip (SOC) and suggest solutions wherever designs, and the Veloce GUI is available. tuned to handle large design databases as well as huge waveform data. Each such set Tcl/Tk commands and rendering of generated debug data having is observed as compared to 8.4 information about design release. Performance hierarchy; waveform and design benchmark data is also connectivity is called a dataset. reported in a separate section. The application uses object Object-oriented programming The paper concludes by sharing provided by [incr Tcl] package, the findings and by providing to support multiple our recommendations on how to simultaneous dataset debug, catch issues during early stages potentially belonging to of migration. different design databases. The code base for Veloce 4.0 Changes required GUI primarily consists of Tcl/Tk and C/C++. Veloce GUI in This section describes in general uses various Tcl/Tk detail various external and packages and required custom internal dependencies requiring build of Tk (8.4) necessitated by resolution. Also, change in usage of [mti Widgets] (TIP 125: various packages (core and Converting between frame and external) resulting in toplevel windows). Over time, regressions are discussed. we have observed various Tcl/Tk related issues in 8.4 have • tk/library/button.tcl: been fixed in 8.5. Also, since 8.5 release of Tcl/Tk has Package: incorporated TIP #125 (using This is part of new subcommands wm manage standard distribution. and wm forget), has various new features and is actively Issue: maintained, migrating from 8.4 Application uses was a necessity. check buton and radio button, and global As with any migration to a variable linked to the major release (8.5 in this case), buttons are specified it's bound to throw challenges using itcl::scope. This during build, implementation caused Tcl exception at and testing stage. The paper runtime. describes the changes required to build process along with Solution: changes to code base. Changes Patch the tcl to code are result of core Tcl/Tk distribution with available changes or due to changes in fix for bug # 87409. This the packages like [incr Tk]. fix uses uplevel set Also, the paper covers areas instead of set ::to work where change in behaviour of with itcl. [info level] with level argument as -1 in order to • [list]-Quoting of the '#' verify that the caller is character: tk::dialog::file. However, this no longer returns the Package: required information in This is part of Tcl/Tk 8.5. standard distribution. Solution: Issue: Level argument Application dumps passed to [info level] the tree contents during should be -2 instead of -1. automated testing to check for new regressions if any. Starting with • [pwd] Tcl/Tk 8.5, name of tree nodes starting with ‘#’ Package: are quoted by default. This is part of standard distribution. Solution: Application could Issue: either modify the routine In Tcl/Tk 8.4 if a dumping the contents of present working directory the tree if possible or gets deleted a call to pwd update the gold files. throws exception. However, starting with Tcl/Tk 8.5 pwd returns an • [info level] empty string and no longer throws exception. Package: This is part of Solution: standard distribution. Add check for empty string on return Issue: value of pwd. Change in information returned by [info level] command. Application in question • [tk_getOpenFile] disables cd command for a user. However, various Package: tk routines like This is part of tk_chooseDirectory, standard distribution. tk_getOpenFile, and tk_getSaveFile internally Issue: call cd. Until Tcl/Tk 8.4 In Tcl/Tk 8.4 application would call multiple file and directory selection using ctrl Package: throws an exception. This is part of standard distribution. Solution: This has been fixed Issue: in Tcl/Tk 8.5. No change Application allows is required in application docking and undocking of code. child windows. This was implemented in Tcl/Tk 8.4 • [incr Tk]: 3.4 using patch for [wm toplevel]. Package: However, this TIP This package is was incorporated into included with [incr Tcl] standard distribution with distribution. new wm subcommands manage and forget. Issue: [incr Tk] supplies Solution: three base classes that A procedure reside in the itk wm_toplevel was defined namespace: to handle all calls to [wm 1. itk::Archetype toplevel]. Following is the 2. itk::Widget definition of the 3. itk::Toplevel procedure. Application uses proc wm_toplevel {win {bool {}}} { [incr Tk] 3.2 with Tcl/Tk if {[llength [info level 8.4 and “–menu” option is 0]] == 2} { defined in base class return [expr {[winfo itk::Archetype. However, manager $win] eq "wm"}] with [incr Tk] 3.4 this } else { if {$bool} { option is now defined only wm manage $win for toplevel windows i.e. } else { itk::Toplevel. wm forget $win } Solution: } } Widgets derived from itk::Archetype will • BWidget: 1.9.2 no longer have “-menu” option defined and will Package: require necessary This package is part changes i.e. use of Tcllib and is itk::Toplevel instead. available at http://tcllib.sf.net/. • [TIP 125]: wm manage and wm forget Issue: Solution: Application was Required changes to using BWidget 1.6 and application code on case many interfaces level by case basis. Above changes have occurred mentioned code had to be since 1.6. The command replaced with Widget::create does the pack $left –expand renaming of the widgets yes –fill both –side left to $path:cmd and creates –padx 5 –pady 5 pack $button_frame – the proc to redirect the dise left –padx 5 –pady 5 widget commands. pack $right –expand yes –fill both –side left Solution: –padx 5 –pady 5 Change usage of BWlabel::create to Label::create. Also, BWidget 1.9.1 release was a development snapshot from the Tile enabled version. This release has • Drag and drop some compatibility issues and users are encouraged to upgrade to 1.9.2. Package: This is part of tkdnd distribution. • Incorrect gridding/packing of elements Issue: Application uses Package: tkdnd for supporting drag This is part of and drop. Incorrect text standard distribution. was dropped in some cases. Issue: This relates to Solution: incorrect display in Tcl/Tk A close inspection 8.5 as compared to 8.4. revealed that unnecessary For example following quoting was causing an would display the middle issue i.e. “%T” instead of element correctly in 8.4 %T in the bind script. but not in 8.5 where button_frame contains • Tk crash while trying to add and remove buttons. pack $left dock/undock a window $button_frame $right – repeatedly. expand yes –fill both – side left =padx –pady 5 Package: This is part of regressions in our test standard distribution. suites. Issue: Solution: Repeated docking Preferences were and undocking of child modified in the windows would result in a application to select a Tk crash. On closer larger font to fix inspection it seemed that regression issues found this was due to change in during automated testing. the way “-menu” option was configured. Most of these child windows were 5.0 Performance derived from itk::Archetype. Also, due Moving to newer to changes to “menu” in release of Tcl/Tk 8.5 has [incr Tk] 3.4, “menu” was caused some unexpected configured after first regressions in terms of undock operation. This performance. In a resulted in abnormal particular computation termination during intensive task (happens docking process. on C/C++ side) it was observed that the Solution: performance penalty can Configure “menu” be as high as 30%. option to empty during all Application is busy with docking operations and the computation and does configure it back to not take user inputs i.e. correct menu during no change in display of undocking. the application. Solution: • Change in font size. Currently we are trying to profile the Package: application in order to This is part of narrow down the exact standard distribution.
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]
  • Tclpro™ User's Guide
    TclPro™ User’s Guide • • • • • • Scriptics Corporation Version 1.3 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 by 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.
    [Show full text]
  • 0:Object-Oriented Programming with [Incr Tcl] 0:Building Mega-Widgets with [Incr
    0:Object-Oriented Programming with [incr Tcl] 0:Building Mega-Widgets with [incr Tk] Michael J. McLennan Bell Labs Innovations for Lucent Technologies 1247 S. Cedar Crest Blvd. Allentown, PA 18104 [email protected] Copyright © 1996 Lucent Technologies ABSTRACT Applications with short development cycles have the best chance for success in today’s marketplace. Tcl/Tk provides an interactive development environment for building Graphical User Interface (GUI) applications with incredible speed. Tcl/Tk applications look like they were constructed with the Motif toolkit, but they can be written in a fraction of the time. This is due, in part, to the high- level programming interface that the Tcl language provides. It is also due to the interpretive nature of the Tcl language; changes made to a Tcl/Tk application can be seen immediately, without waiting for the usual compile/link/run cycle. Developers can prototype new ideas, review them with customers, and deliver a finished product within a span of several weeks. The finished product will run on all of the major platforms: Unix, PC Windows, and Macintosh. But the Tcl language was not designed to support large programming projects. When Tcl/Tk scripts grow larger than a thousand lines, the code complexity can be difficult to manage. [INCR TCL] extends the Tcl language to support object- oriented programming. This allows developers to write high-level building blocks that are more easily assembled into a finished application. The resulting code has more encapsulation, and is easier to maintain and extend. [INCR TCL] is patterned after C++, so for many developers, it is easy to learn.
    [Show full text]
  • The (Active) State of Tcl
    The (Active) State of Tcl 15th Annual Tcl Conference (2008) Jeff Hobbs Director, Languages ActiveState Corporation Agenda Introduction What has happened… Developments in the Tcl community The Active State Developments of the Tcl/Tk core Future directions About ActiveState ActiveState Software Inc. Over 10 years focusing on open source dynamic languages Independent again since February, 2006 ActiveState provides multi-language, cross-platform software & services Tcl, Perl, PHP, Python, Ruby AIX, HP-UX, Linux, Mac OS X, Solaris, Windows, … Comprehensive Software Stacks for Dynamic Languages Make programming easier using dynamic languages Active distributions Software development tools (IDEs, Dev Kits) Programmer resources (ASPN) Enterprise support & OEM redistribution History of Tcl 1. Tcl created as general-purpose 4. Scriptics formed: command/scripting language by 7. ActiveState introduces • Evolve and extend Tcl platform Tcl support and services John Ousterhout • Create development tools 6.0 Sept 7.0 Sept 7.4 July 7.6 Oct 8.0 Aug 8.1 Apr 8.3 Feb 8.4 Sept 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 … 8.2 Aug 5. Tcl Core Team 8.3.5 EOL Oct formed (August) 2. Open source distributions from U.C. Berkeley: 6. Scriptics/Ajuba Acquired • Easy GUIs under Unix by Interwoven (Nov) • Extensible applications 3. Tcl enhanced at Sun Microsystems: 8. ActiveState acquired by • Windows, Macintosh ports Sophos (Sept) • Web/Internet support • Java support Recent History of Tcl Sophos Acquires ActiveState
    [Show full text]
  • 7Th USENIX Tcl/Tk Conference February 14-18, 2000 Austin, Texas, USA
    7th USENIX Tcl/Tk Conference February 14-18, 2000 Austin, Texas, USA Tutorial Sessions Monday, Feb. 14 to Tuesday, Feb. 15, 2000 Please select one morning and one afternoon tutorial. Sorry, no partial registrations are allowed. Monday, February 14, 2000 Morning Sessions (9:00 am - 12:30 pm) M1am: Effective Tcl/Tk Programming Michael McLennan, Cadence Design Systems, Inc. Who should attend: Programmers and managers who are using Tcl/Tk to build real-world applications. This tutorial assumes a working knowledge of Tcl/Tk and goes beyond that to show how nontrivial Tcl/Tk programs are put together. Topics include: • How to use the Tk canvas widget to synthesize new types of widgets • How to use binding tags to add new widget behaviors • How to organize Tcl code into reusable libraries and packages. These techniques come together to create professional-looking applications that are easier to maintain and extend. Michael McLennan has been a Tcl/Tk enthusiast since 1992. He has taught more than 100 Tcl/Tk courses, and is co-author of Effective Tcl/Tk Programming and Tcl/Tk Tools. He also developed [incr Tcl], an object-oriented extension of Tcl/Tk. Michael, who received a Ph.D. in 1990 from Purdue University, is currently an Architect at Cadence Design Systems, Inc. M2am: XML and Tcl/Tk Steve Ball, Zveno Pty. Ltd. Who should attend: Developers who wish to add XML support to their applications, use XML for storing data, or process XML documents using Tcl. XML is set to revolutionize not only the Web but also many industries and businesses, as it allows easy, robust data exchange between machines.
    [Show full text]
  • Medical Image Analysis with VTK: a Tutorial
    Medical Image Analysis with VTK: A Tutorial Xenophon Papademetris December 13, 2006 Departments of Biomedical Engineering and Diagnostic Radiology, Yale University, New Haven, CT 06520-8042. www.bioimagesuite.org Abstract This paper describes a new tutorial book titled “An Introduction to Programming for Medical Im- age Analysis with the Visualization Toolkit.” This book derived from a set of class handouts used in a biomedical engineering graduate seminar at Yale University. The goal for the seminar was to introduce the students to the Visualization Toolkit (VTK) and, to a lesser extent, the Insight Toolkit (ITK). A draft version of the complete book (including all the sample code) is available online at www.bioimagesuite.org/vtkbook. Contents 1 Introduction 1 2 Motivation 2 3 Book Contents 3 4 Conclusions 4 1 Introduction While both the Visualization Toolkit (VTK)[9] and the Insight Toolkit (ITK) [2] come with excellent online documentation, there is still a great need for introductory material to guide the beginner along the often steep learning curve required to learn using these toolkits. This article summarizes the contents of a book in preparation[6], a draft version of which is available freely online in .pdf format from the BioImage Suite web-page. The goal of this book was precisely to fill that void in the availability of introductory material. This book builds on a previous similarly named tutorial [5] that many have found useful in the past. 2 This book is an edited collection of class handouts that I wrote for the graduate seminar “Programming for Medical Image Analysis” (ENAS 920a) that was taught at Yale University, De- partment of Biomedical Engineering, in the Fall of 2006.
    [Show full text]
  • Poet: an OOP Extension to Tcl Supporting Constraints, Persistence, and End-User Modification Philip J
    Poet: An OOP Extension to Tcl Supporting Constraints, Persistence, and End-User Modification Philip J. Mercurio Thyrd.org [email protected] Abstract Integrated Construction Set) supports end-user inspection and modification of a running application. The primary tool is an object browser that displays an object's attributes Poet (Prototype Object Extension for Tcl) extends the Tcl (called slots), methods, constraints, and relationships to language with objects featuring dynamic, prototype-based other objects. Poetics also employs Poet's optional type inheritance, persistence, and one-way constraints between annotation feature so that appropriate content-specific object attributes. Poet includes wrappers around the Tk and editors can be created to edit slot values. A syntax- BWidget widgets that are automatically generated using highlighting code editor allows an application's source code introspection. This paper also describes Poetics (Poet to be edited, saved, and reloaded in a running application. Integrated Construction Set), a sub-project within Poet to create tools to allow a Poet application's code and user As of this writing, the Poetics tools are incomplete and not interface to be modified by the end-user, from within a ready for end-user use. However, even in its current, running Poet application. The goal of Poetics is to provide limited form Poetics can be very useful to the Poet some of the functionality of an integrated development application developer. environment to the user of a Poet application. An object inspector and code editor are the beginnings of the Poetics Related Work toolset. The primary inspiration for Poet is Self [2], a dynamic object-oriented programming language and environment.
    [Show full text]
  • The Book in a Compressed .Pdf Format (1.9MB)
    c Copyright 2009 by Xenophon Papademetris and Alark Joshi All Rights Reserved This book is an edited collection of class handouts that was written for the graduate seminar “Programming for Medical Image Analysis” (ENAS 920a). This class was taught at Yale University, Department of Biomedical Engineering, in the Fall of 2006 and again in the Spring 2009 semester. Some the comments in this draft version of the book reflect this fact. For example, see comments beginning “at Yale”. Furthermore, many of the references that will appear in the final version are still omitted. It is made available at this stage in the hope that it will be useful. Draft Sep. 2009 Contents Preface 5 Preface to the First Edition 6 I Introduction 8 1. Introduction 9 2. Revision Control with Subversion 14 II Programming with Tcl/Tk 19 3. Introduction to Tcl 20 4. Advanced Topics in Tcl 28 5. An Introduction To Tk 35 6. Tk Part II 43 7. Object Oriented Programming with [ Incr ] Tcl 53 8. Iwidgets: Object Oriented Programming for GUIs 63 III The Visualization Toolkit I – Using Tcl 70 9. An Introduction to the Visualization Toolkit 71 10.Curves and Surfaces in VTK 75 11.Images in VTK 85 12.Displaying Images in VTK 92 13.Transforming Surfaces and Reslicing Images 104 3 CONTENTS Draft Sep. 2009 IV Interfacing To BioImage Suite using Tcl 114 14.Leveraging BioImage Suite Components and Classes 115 15.Writing your own BioImage Suite Tcl Application 125 16.BIS Algorithm Framework 152 V C++ Techniques 169 17.Cross-Platform Compiling with CMAKE 170 18.C++ Techniques and VTK 177 VI VTK Programming with C++ and Tcl 189 19.VTK Code in C++: Procedural Code and Derived Classes 190 20.Implementing Point-Based Registration 202 21.Implementing Intensity Based Segmentation 220 22.More Advanced Image Algorithm/Filters and Templated Execution 239 23.Copying Data Objects and Breaking the Pipeline 251 24.The Insight Toolkit 256 VII Appendices 267 A.
    [Show full text]
  • CS 520 – Principles of Programming Languages a Report on Tcl/Tk Balaji Ramamurthy – [email protected] Xuchen Wang –
    CS 520 – Principles of Programming Languages A Report on Tcl/Tk Balaji Ramamurthy – [email protected] Xuchen Wang – [email protected] TABLE of CONTENTS Topic Page 1. INTRODUCTION 2 2. FEATURES of Tcl/Tk 2 2.1. The interpreted nature of Tcl 2 2.2. Syntax 3 2.3. Scope rules in Tcl 4 2.4. Procedures 4 2.5. Call by value and reference 4 2.6. Conditionals 5 2.7. Iterators 5 2.8. Error and Exception Handling 6 3. EMBEDDABILITY and EXTENSIBILITY 7 4. OBJECT ORIENTED? 7 5. MEMORY MANAGEMENT and GARBAGE COLLECTION 7 6. ADVANCED CONCEPTS 8 7. Tk - THE CROSS-PLATFORM TOOLKIT 9 8. SUMMARY and CONCLUSION 10 9. REFERCENCES 10 1. INTRODUCTION Tcl (pronounced as "tickle" or "tee-cee-ell") is a scripting language. Tcl was created by Professor John Ousterhout of the University of California, Berkeley. Tcl is believed to be a programming language that is easy to learn. It is a general purpose scripting language originally intended to be embedded in other applications as a configuration and extension language. Tcl is a dynamic, string oriented language, which makes it an ideal candidate for developing web applications. It also has the ability to interact seamlessly with other software and hardware, which makes it a great choice in the area of testing and automation. Tcl also has many packages and extensions that enable to integrate with the majority of the standard databases available in the market. It can also seamlessly integrate with embedded databases using these packages and extensions. Due to the presence of such fantastic features as mentioned above, Tcl is the most popular choice for embedded development.
    [Show full text]
  • Visual Programming of the ITK Image Processing Library Within Simulink
    SimITK: Visual Programming of the ITK Image Processing Library within Simulink by Andrew William Laird Dickinson A thesis submitted to the School of Computing in conformity with the requirements for the degree of Master of Science Queen's University Kingston, Ontario, Canada September 2011 Copyright c Andrew William Laird Dickinson, 2011 Abstract The Insight Segmentation and Registration Toolkit (ITK) is a long-established image processing library used for image analysis, visualisation, and image-guided surgery applications. ITK is a collection of C++ classes that can potentially pose usability problems for users without appropriate C++ programming experience. In order to remove the programming complexities and facilitate rapid prototyping, an implemen- tation of ITK within a higher-level visual programming environment is presented: SimITK. ITK functionalities are automatically wrapped into \blocks" within the vi- sual programming environment of MATLAB, Simulink, where these blocks can be connected to form workflows: visual schematics that closely represent the structure of a C++ program. The heavily C++ templated nature of ITK does not facilitate direct interaction be- tween Simulink and ITK; an intermediary is required to convert respective datatypes and allow intercommunication. As such, a SimITK \Virtual Block" has been de- veloped that serves as a wrapper around the ITK class responsible for resolving the datatypes used by ITK to native types used by Simulink. Part of this challenge sur- rounds the automated capturing and storage of the pertinent class information (name, inputs/outputs, acceptable datatypes, and allowed dimensionalities) that needs to be reflected within the final block representation. The WrapITK package, included with i ITK, serves to generate initial class representations as complex eXtended Markup Language (XML) files that are consolidated and refined to organise the information into an easily accessible structure when extracting during wrapping.
    [Show full text]
  • TCL/TK ELECTRONIC REFERENCE for Tcl /Tk Version 8.0.X and [Incr Tcl] Version 3.0
    TCL/TK ELECTRONIC REFERENCE for Tcl /Tk version 8.0.x and [incr Tcl] version 3.0 Coverted to Adobe Acrobat Format (.pdf) by Charles Todd, Oct 1998. [email protected] BUILT-IN Tcl APPLICATIONS CLIBRARYIBRARY BUILT-IN TK APPLICATIONS CLIBRARYIBRARY [INCRINCR TCL] [INCRINCR WIDGETSIDGETS] [INCR TK] Tcl Applications tclsh ( 1 ) NAME tclsh − Simple shell containing Tcl interpreter SYNOPSIS tclsh ?fileName arg arg ...? DESCRIPTION Tclsh is a shell-like application that reads Tcl commands from its standard input or from a file and evalu- ates them. If invoked with no arguments then it runs interactively, reading Tcl commands from standard input and printing command results and error messages to standard output. It runs until the exit command is invoked or until it reaches end-of-file on its standard input. If there exists a file .tclshrc in the home directory of the user, tclsh evaluates the file as a Tcl script just before reading the first command from stan- dard input. SCRIPT FILES If tclsh is invoked with arguments then the first argument is the name of a script file and any additional arguments are made available to the script as variables (see below). Instead of reading commands from standard input tclsh will read Tcl commands from the named file; tclsh will exit when it reaches the end of the file. There is no automatic evaluation of .tclshrc in this case, but the script file can always source it if desired. If you create a Tcl script in a file whose first line is #!/usr/local/bin/tclsh then you can invoke the script file directly from your shell if you mark the file as executable.
    [Show full text]
  • Comparing Selected Criteria of Programming Languages Java, PHP, C++, Perl, Haskell, Aspectj, Ruby, COBOL, Bash Scripts and Scheme Revision 1.0 Sultan S
    Comparing Selected Criteria of Programming Languages Java, PHP, C++, Perl, Haskell, AspectJ, Ruby, COBOL, Bash Scripts and Scheme Revision 1.0 Sultan S. Al-Qahtani Luis F. Guzman Concordia University Concordia University Montreal, Quebec, Canada Montreal, Quebec, Canada [email protected] [email protected] Rafik Arif Adrien Tevoedjre Concordia University Concordia University Montreal, Quebec, Canada Montreal, Quebec, Canada [email protected] [email protected] Pawel Pietrzynski Concordia University Montreal, Quebec, Canada [email protected] Abstract Comparison of programming languages is a common topic of discussion among software engineers. Few languages ever become sufficiently popular that they are used by more than a few people or find their niche in research or education; but professional programmers can easily use dozens of different languages during their career. Multiple programming languages are designed, specified, and implemented every year in order to keep up with the changing programming paradigms, hardware evolution, etc. In this paper we present a comparative study between ten programming languages: Haskell, Java, Perl, C++, AspectJ, COBOL, Ruby, PHP, Bash Scripts, and Scheme; with respect of the following criteria: Secure programming practices, web applications development, web services design and composition, object oriented-based abstraction, reflection, aspect-orientation, functional programming, declarative programming, batch scripting, and user interface prototype design. 1. Introduction The first high-level programming languages were designed during the 1950s. Ever since then, programming languages have been a fascinating and productive area of study [43]. Thousands of different programming languages have been created, mainly in the computer field, with many more being created every year; they are designed, specified, and implemented for the purpose of being up to date with the evolving programming paradigms (e.g.
    [Show full text]