CORBA Scripting Language Specification

Total Page:16

File Type:pdf, Size:1020Kb

CORBA Scripting Language Specification CORBA Scripting Language Specification Version 1.0 June 2001 Copyright © 1997-99 Laboratoire d’Informatique Fondamentale de Lille Copyright © 2001 Object Management Group Copyright © 1997-99 Object–Oriented Concepts, Inc. The companies listed above have granted to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version. Each of the copyright holders listed above has agreed that no person shall be deemed to have infringed the copyright in the included material of any such copyright holder by reason of having used the specification set forth herein or having conformed any computer software to the specification. PATENT The attention of adopters is directed to the possibility that compliance with or adoption of OMG specifications may require use of an invention covered by patent rights. OMG shall not be responsible for identifying patents for which a license may be required by any OMG specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OMG specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents. NOTICE The information contained in this document is subject to change without notice. The material in this document details an Object Management Group specification in accordance with the license and notices set forth on this page. This document does not represent a commitment to implement any portion of this specification in any company's products. WHILE THE INFORMATION IN THIS PUBLICATION IS BELIEVED TO BE ACCURATE, THE OBJECT MANAGEMENT GROUP AND THE COMPANIES LISTED ABOVE MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS MATERIAL INCLUDING, BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR PARTICULAR PURPOSE OR USE. In no event shall The Object Management Group or any of the companies listed above be liable for errors contained herein or for indirect, incidental, special, consequential, reliance or cover damages, including loss of profits, revenue, data or use, incurred by any user or any third party. The copyright holders listed above acknowledge that the Object Management Group (acting itself or through its designees) is and shall at all times be the sole entity that may authorize developers, suppliers and sellers of computer software to use certification marks, trademarks or other special designations to indicate compliance with these materials. This document contains information which is protected by copyright. All Rights Reserved. No part of this work covered by copyright herein may be reproduced or used in any form or by any means--graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems--without permission of the copyright owner. RESTRICTED RIGHTS LEGEND. Use, duplication, or disclosure by government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Right in Technical Data and Computer Software Clause at DFARS 252.227.7013 OMG®and Object Management are registered trademarks of the Object Management Group, Inc. Object Request Broker, OMG IDL, ORB, CORBA, CORBAfacilities, CORBAservices, COSS, and IIOP are trademarks of the Object Management Group, Inc. X/Open is a trademark of X/Open Company Ltd. ISSUE REPORTING All OMG specifications are subject to continuous review and improvement. As part of this process we encourage readers to report any ambiguities, inconsistencies, or inaccuracies they may find by completing the issue reporting form at http://www.omg.org/library/issuerpt.htm. Contents Preface . vii 1. IDLscript Overview. 1-1 1.1 Scripting Languages. 1-1 1.2 CORBA and Scripting Languages . 1-2 1.3 The IDLscript Language . 1-3 1.4 An IDLscript Example . 1-6 1.4.1 A Grid Distributed Application . 1-6 1.4.2 Basic Functionalities . 1-7 1.4.3 Dynamic CORBA Connection . 1-8 1.4.4 Direct Access to all OMG IDL Definitions . 1-8 1.4.5 Connection to Any CORBA Object . 1-9 1.4.6 OMG IDL Operations, Attributes, and Exceptions1-9 1.4.7 Procedures and Modules. 1-10 1.4.8 Implementation of OMG IDL Interfaces . 1-11 1.4.9 Creation of Stand-alone CORBA Servers . 1-14 1.4.10 Conclusion . 1-14 2. The IDLscript Language Core . 2-1 2.1 Overview . 2-2 2.2 Lexical Conventions. 2-2 2.2.1 Tokens . 2-3 2.2.2 Comments. 2-3 2.2.3 Identifiers . 2-3 2.2.4 Keywords . 2-4 2.2.5 Literals . 2-4 June 2001 CORBA Scripting Language i Contents 2.3 IDLscript Grammar . 2-6 2.4 Scripts . 2-9 2.5 Expressions . 2-9 2.5.1 Syntax. 2-10 2.5.2 Literal Values . 2-10 2.5.3 Identifiers . 2-11 2.5.4 Arithmetic Operators . 2-11 2.5.5 Relational Operators. 2-12 2.5.6 Logical Operators . 2-12 2.5.7 Procedural Call . 2-13 2.5.8 Attribute Getting. 2-13 2.5.9 Method Call . 2-13 2.5.10 Array Creation . 2-14 2.5.11 Dictionary Creation . 2-14 2.5.12 Indexed Getting . 2-14 2.6 Variable and Attribute Management. 2-14 2.6.1 Assignments . 2-15 2.6.2 The Del Statement. 2-15 2.7 Objects and Types . 2-15 2.7.1 Everything is Typed Object . 2-15 2.7.2 Basic Value Types. 2-16 2.7.3 String Objects . 2-17 2.7.4 Array Objects . 2-19 2.7.5 Dictionary Objects . 2-21 2.7.6 Predefined Internal Procedures. 2-22 2.8 Control Flow Statements . 2-23 2.8.1 Syntax. 2-23 2.8.2 The If Statement . 2-23 2.8.3 The While Statement . 2-24 2.8.4 The Do Statement . 2-24 2.8.5 The For Statement. 2-25 2.8.6 The Return Statement . 2-25 2.9 Procedures . 2-26 2.9.1 Declaration . 2-26 2.9.2 Formal Parameters and Default Values . 2-26 2.9.3 The Returned Object. 2-27 2.9.4 Local and Global Variables. 2-27 2.9.5 Procedure Aliasing . 2-28 2.10 Classes . 2-28 2.10.1 Declaration . 2-28 ii CORBA Scripting Language June 2001 Contents 2.10.2 A Simple Class Example . 2-29 2.10.3 A Single Class Inheritance Example . 2-31 2.10.4 A Multiple Class Inheritance Example . 2-31 2.10.5 Class and Instance Types . 2-32 2.11 Exceptions . 2-32 2.11.1 Internal Exceptions. 2-32 2.11.2 User Exceptions . 2-34 2.11.3 Exception Handling . 2-35 2.12 Modules . 2-36 2.12.1 Importation. 2-36 2.12.2 Initialization . 2-37 2.12.3 Access to the Content . 2-37 2.12.4 Module Aliasing . 2-37 2.12.5 Module Management . 2-37 3. The OMG IDL Binding. 3-1 3.1 Overview . 3-2 3.2 Binding for Basic OMG IDL Types . 3-2 3.2.1 IDLscript Representation . 3-3 3.2.2 Basic OMG IDL Values . 3-3 3.3 Binding for OMG IDL Module . 3-4 3.3.1 OMG IDL Examples . 3-4 3.3.2 IDLscript Representation . 3-4 3.4 Binding for OMG IDL Constant . 3-4 3.4.1 OMG IDL Examples . 3-4 3.4.2 IDLscript Representation . 3-5 3.5 Binding for OMG IDL Enum. 3-5 3.5.1 An OMG IDL Example . 3-5 3.5.2 IDLscript Representation . 3-6 3.5.3 Enum Values. 3-6 3.6 Binding for OMG IDL Structure . 3-6 3.6.1 OMG IDL Examples . 3-7 3.6.2 IDLscript Representation . 3-7 3.6.3 Structure Values . 3-8 3.6.4 Structure Fields . 3-8 3.7 Binding for OMG IDL Union. 3-9 3.7.1 An OMG IDL Example . 3-9 3.7.2 IDLscript Representation . 3-9 3.7.3 Union Values . 3-9 3.7.4 Union Fields . 3-10 June 2001 CORBA Scripting Language iii Contents 3.8 Binding for OMG IDL Typedef . 3-11 3.8.1 OMG IDL Examples . 3-11 3.8.2 IDLscript Representation . 3-11 3.8.3 Typedef Values . 3-11 3.9 Binding for OMG IDL Sequence . 3-12 3.9.1 OMG IDL Examples . 3-12 3.9.2 IDLscript Representation . 3-12 3.9.3 Sequence Values . ..
Recommended publications
  • Chapter 12 Calc Macros Automating Repetitive Tasks Copyright
    Calc Guide Chapter 12 Calc Macros Automating repetitive tasks Copyright This document is Copyright © 2019 by the LibreOffice Documentation Team. Contributors are listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (http://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (http://creativecommons.org/licenses/by/4.0/), version 4.0 or later. All trademarks within this guide belong to their legitimate owners. Contributors This book is adapted and updated from the LibreOffice 4.1 Calc Guide. To this edition Steve Fanning Jean Hollis Weber To previous editions Andrew Pitonyak Barbara Duprey Jean Hollis Weber Simon Brydon Feedback Please direct any comments or suggestions about this document to the Documentation Team’s mailing list: [email protected]. Note Everything you send to a mailing list, including your email address and any other personal information that is written in the message, is publicly archived and cannot be deleted. Publication date and software version Published December 2019. Based on LibreOffice 6.2. Using LibreOffice on macOS Some keystrokes and menu items are different on macOS from those used in Windows and Linux. The table below gives some common substitutions for the instructions in this chapter. For a more detailed list, see the application Help. Windows or Linux macOS equivalent Effect Tools > Options menu LibreOffice > Preferences Access setup options Right-click Control + click or right-click
    [Show full text]
  • Rexx Programmer's Reference
    01_579967 ffirs.qxd 2/3/05 9:00 PM Page i Rexx Programmer’s Reference Howard Fosdick 01_579967 ffirs.qxd 2/3/05 9:00 PM Page iv 01_579967 ffirs.qxd 2/3/05 9:00 PM Page i Rexx Programmer’s Reference Howard Fosdick 01_579967 ffirs.qxd 2/3/05 9:00 PM Page ii Rexx Programmer’s Reference Published by Wiley Publishing, Inc. 10475 Crosspoint Boulevard Indianapolis, IN 46256 www.wiley.com Copyright © 2005 by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN: 0-7645-7996-7 Manufactured in the United States of America 10 9 8 7 6 5 4 3 2 1 1MA/ST/QS/QV/IN No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4355, e-mail: [email protected]. LIMIT OF LIABILITY/DISCLAIMER OF WARRANTY: THE PUBLISHER AND THE AUTHOR MAKE NO REPRESENTATIONS OR WARRANTIES WITH RESPECT TO THE ACCURACY OR COM- PLETENESS OF THE CONTENTS OF THIS WORK AND SPECIFICALLY DISCLAIM ALL WAR- RANTIES, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE.
    [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]
  • 10 Programming Languages You Should Learn Right Now by Deborah Rothberg September 15, 2006 8 Comments Posted Add Your Opinion
    10 Programming Languages You Should Learn Right Now By Deborah Rothberg September 15, 2006 8 comments posted Add your opinion Knowing a handful of programming languages is seen by many as a harbor in a job market storm, solid skills that will be marketable as long as the languages are. Yet, there is beauty in numbers. While there may be developers who have had riches heaped on them by knowing the right programming language at the right time in the right place, most longtime coders will tell you that periodically learning a new language is an essential part of being a good and successful Web developer. "One of my mentors once told me that a programming language is just a programming language. It doesn't matter if you're a good programmer, it's the syntax that matters," Tim Huckaby, CEO of San Diego-based software engineering company CEO Interknowlogy.com, told eWEEK. However, Huckaby said that while his company is "swimmi ng" in work, he's having a nearly impossible time finding recruits, even on the entry level, that know specific programming languages. "We're hiring like crazy, but we're not having an easy time. We're just looking for attitude and aptitude, kids right out of school that know .Net, or even Java, because with that we can train them on .Net," said Huckaby. "Don't get fixated on one or two languages. When I started in 1969, FORTRAN, COBOL and S/360 Assembler were the big tickets. Today, Java, C and Visual Basic are. In 10 years time, some new set of languages will be the 'in thing.' …At last count, I knew/have learned over 24 different languages in over 30 years," Wayne Duqaine, director of Software Development at Grandview Systems, of Sebastopol, Calif., told eWEEK.
    [Show full text]
  • Safe, Fast and Easy: Towards Scalable Scripting Languages
    Safe, Fast and Easy: Towards Scalable Scripting Languages by Pottayil Harisanker Menon A dissertation submitted to The Johns Hopkins University in conformity with the requirements for the degree of Doctor of Philosophy. Baltimore, Maryland Feb, 2017 ⃝c Pottayil Harisanker Menon 2017 All rights reserved Abstract Scripting languages are immensely popular in many domains. They are char- acterized by a number of features that make it easy to develop small applications quickly - flexible data structures, simple syntax and intuitive semantics. However they are less attractive at scale: scripting languages are harder to debug, difficult to refactor and suffers performance penalties. Many research projects have tackled the issue of safety and performance for existing scripting languages with mixed results: the considerable flexibility offered by their semantics also makes them significantly harder to analyze and optimize. Previous research from our lab has led to the design of a typed scripting language built specifically to be flexible without losing static analyzability. Inthis dissertation, we present a framework to exploit this analyzability, with the aim of producing a more efficient implementation Our approach centers around the concept of adaptive tags: specialized tags attached to values that represent how it is used in the current program. Our frame- work abstractly tracks the flow of deep structural types in the program, and thuscan ii ABSTRACT efficiently tag them at runtime. Adaptive tags allow us to tackle key issuesatthe heart of performance problems of scripting languages: the framework is capable of performing efficient dispatch in the presence of flexible structures. iii Acknowledgments At the very outset, I would like to express my gratitude and appreciation to my advisor Prof.
    [Show full text]
  • Complementary Slides for the Evolution of Programming Languages
    The Evolution of Programming Languages In Text: Chapter 2 Programming Language Genealogy 2 Zuse’s Plankalkül • Designed in 1945, but not published until 1972 • Never implemented • Advanced data structures – floating point, arrays, records • Invariants 3 Plankalkül Syntax • An assignment statement to assign the expression A[4] + 1 to A[5] | A + 1 => A V | 4 5 (subscripts) S | 1.n 1.n (data types) 4 Minimal Hardware Programming: Pseudocodes • Pseudocodes were developed and used in the late 1940s and early 1950s • What was wrong with using machine code? – Poor readability – Poor modifiability – Expression coding was tedious – Machine deficiencies--no indexing or floating point 5 Machine Code • Any binary instruction which the computer’s CPU will read and execute – e.g., 10001000 01010111 11000101 11110001 10100001 00010101 • Each instruction performs a very specific task, such as loading a value into a register, or adding two binary numbers together 6 Short Code: The First Pseudocode • Short Code developed by Mauchly in 1949 for BINAC computers – Expressions were coded, left to right – Example of operations: 01 – 06 abs value 1n (n+2)nd power 02 ) 07 + 2n (n+2)nd root 03 = 08 pause 4n if <= n 04 / 09 ( 58 print and tab 7 • Variables were named with byte-pair codes – E.g., X0 = SQRT(ABS(Y0)) – 00 X0 03 20 06 Y0 – 00 was used as padding to fill the word 8 IBM 704 and Fortran • Fortran 0: 1954 - not implemented • Fortran I: 1957 – Designed for the new IBM 704, which had index registers and floating point hardware • This led to the idea of compiled
    [Show full text]
  • The World of Scripting Languages Pdf, Epub, Ebook
    THE WORLD OF SCRIPTING LANGUAGES PDF, EPUB, EBOOK David Barron | 506 pages | 02 Aug 2000 | John Wiley & Sons Inc | 9780471998860 | English | New York, United States The World of Scripting Languages PDF Book How to get value of selected radio button using JavaScript? She wrote an algorithm for the Analytical Engine that was the first of its kind. There is no specific rule on what is, or is not, a scripting language. Most computer programming languages were inspired by or built upon concepts from previous computer programming languages. Anyhow, that led to me singing the praises of Python the same way that someone would sing the praises of a lover who ditched them unceremoniously. Find the best bootcamp for you Our matching algorithm will connect you to job training programs that match your schedule, finances, and skill level. Java is not the same as JavaScript. Found on all windows and Linux servers. All content from Kiddle encyclopedia articles including the article images and facts can be freely used under Attribution-ShareAlike license, unless stated otherwise. Looking for more information like this? Timur Meyster in Applying to Bootcamps. Primarily, JavaScript is light weighed, interpreted and plays a major role in front-end development. These can be used to control jobs on mainframes and servers. Recover your password. It accounts for garbage allocation, memory distribution, etc. It is easy to learn and was originally created as a tool for teaching computer programming. Kyle Guercio - January 21, 0. Data Science. Java is everywhere, from computers to smartphones to parking meters. Requires less code than modern programming languages.
    [Show full text]
  • Comparative Studies of 10 Programming Languages Within 10 Diverse Criteria Revision 1.0
    Comparative Studies of 10 Programming Languages within 10 Diverse Criteria Revision 1.0 Rana Naim∗ Mohammad Fahim Nizam† Concordia University Montreal, Concordia University Montreal, Quebec, Canada Quebec, Canada [email protected] [email protected] Sheetal Hanamasagar‡ Jalal Noureddine§ Concordia University Montreal, Concordia University Montreal, Quebec, Canada Quebec, Canada [email protected] [email protected] Marinela Miladinova¶ Concordia University Montreal, Quebec, Canada [email protected] Abstract This is a survey on the programming languages: C++, JavaScript, AspectJ, C#, Haskell, Java, PHP, Scala, Scheme, and BPEL. Our survey work involves a comparative study of these ten programming languages with respect to the following criteria: secure programming practices, web application development, web service composition, OOP-based abstractions, reflection, aspect orientation, functional programming, declarative programming, batch scripting, and UI prototyping. We study these languages in the context of the above mentioned criteria and the level of support they provide for each one of them. Keywords: programming languages, programming paradigms, language features, language design and implementation 1 Introduction Choosing the best language that would satisfy all requirements for the given problem domain can be a difficult task. Some languages are better suited for specific applications than others. In order to select the proper one for the specific problem domain, one has to know what features it provides to support the requirements. Different languages support different paradigms, provide different abstractions, and have different levels of expressive power. Some are better suited to express algorithms and others are targeting the non-technical users. The question is then what is the best tool for a particular problem.
    [Show full text]
  • Webscript – a Scripting Language for the Web
    WebScript – A Scripting Language for the Web Yin Zhang Cornell Network Research Group (CNRG) Department of Computer Science Cornell University Ithaca, NY 14853, U.S.A. E-mail: [email protected] Abstract WebScript is a scripting language for processing Web documents. Designed as an extension to Jacl, the Java implementation of Tcl, WebScript allows programmers to manipulate HTML in the same way as Tcl manipulates text strings and GUI elements. This leads to a completely new way of writing the next generation of Web applications. This paper presents the motivation behind the design and implementation of WebScript , an overview of its major features, as well as some demonstrations of its power. 1 Introduction WebScript is a scripting language for processing Web documents. It is designed and implemented as an extension to Jacl [10, 11], the Java [1] implementation of Tcl [17]. With a concise set of commands and library routines, WebScript allows programmers to manipulate HTML [9] in the same way as Tcl manipulates text strings and GUI elements. Meanwhile, the underlying integration of Java and Tcl technologies allows programmers to have all the goodies of both Java and Tcl for free. In addition, WebScript provides useful language features like pipe, threads etc. that greatly simplify the task of programming. We believe that all these features have made WebScript an ideal language for quick prototyping and developing the next generation of Web applications. This paper presents the motivation behind the design and implementation of WebScript , an overview of its major language features, as well as some demonstrations of its power.
    [Show full text]
  • The PLT Course at Columbia
    Alfred V. Aho [email protected] The PLT Course at Columbia Guest Lecture PLT September 10, 2014 Outline • Course objectives • Language issues • Compiler issues • Team issues Course Objectives • Developing an appreciation for the critical role of software in today’s world • Discovering the principles underlying the design of modern programming languages • Mastering the fundamentals of compilers • Experiencing an in-depth capstone project combining language design and translator implementation Plus Learning Three Vital Skills for Life Project management Teamwork Communication both oral and written The Importance of Software in Today’s World How much software does the world use today? Guesstimate: around one trillion lines of source code What is the sunk cost of the legacy software base? $100 per line of finished, tested source code How many bugs are there in the legacy base? 10 to 10,000 defects per million lines of source code Alfred V. Aho Software and the Future of Programming Languages Science, v. 303, n. 5662, 27 February 2004, pp. 1331-1333 Why Take Programming Languages and Compilers? To discover the marriage of theory and practice To develop computational thinking skills To exercise creativity To reinforce robust software development practices To sharpen your project management, teamwork and communication (both oral and written) skills Why Take PLT? To discover the beautiful marriage of theory and practice in compiler design “Theory and practice are not mutually exclusive; they are intimately connected. They live together and support each other.” [D. E. Knuth, 1989] Theory in practice: regular expression pattern matching in Perl, Python, Ruby vs. AWK Running time to check whether a?nan matches an regular expression and text size n Russ Cox, Regular expression matching can be simple and fast (but is slow in Java, Perl, PHP, Python, Ruby, ...) [http://swtch.com/~rsc/regexp/regexp1.html, 2007] Computational Thinking – Jeannette Wing Computational thinking is a fundamental skill for everyone, not just for computer scientists.
    [Show full text]
  • Using a Scripting Language for Dynamic Programming
    AC 2008-2623: USING A SCRIPTING LANGUAGE FOR DYNAMIC PROGRAMMING Louis Plebani, Lehigh University Page 13.1325.1 Page © American Society for Engineering Education, 2008 Using a Scripting Language for Dynamic Programming Abstract In this paper we present a simple programming framework that can be used in teaching Dynamic Programming at an introductory level. The target audience for the framework is the student in an introduction to dynamic programming setting who possesses rudimentary programming skills. The framework takes advantage of the late binding features of the Python scripting language to allow students to model their problem with somewhat arbitrary data types and and to subsequently solve without worrying about more complex computer programming issues. Introduction Dynamic programming (DP) is a versatile technique for modeling and solving sequential optimization problems. While the approach is well known to the operations research community, its impact has been limited when compared to other mathematical programming techniques such as linear programming. Ironically, in part, this has been due to its flexibility. Because DP can be adapted to a myriad of problems and those models can be implemented in a variety of ways, many modelers, particulary inexperienced ones, are overwhelmed by the large number of choices. This is often referred to as the “art” of dynamic programming. Our goal was to provide a framework and base computer code for students to achieve an ease of modeling and solution for dynamic programming similar to what has been achieved for linear programming. In so far as the teaching dynamic programming, this will allow educators in operations research to focus their teaching on issues relevant to dynamic programming as opposed to computer programming issues; and allow students in operations research to focus their learning on the power of dynamic programming, as opposed to the nuances of computer implementations.
    [Show full text]
  • CAD Scripting and Visual Programming Languages For
    CAD Scripting And Visual Programming Languages For Implementing Computational Design Concepts:A Comparison From A Pedagogical Point Of View Gabriela Celani and Carlos Eduardo Verzola Vaz international journal of architectural computing issue 01, volume 10 121 CAD Scripting And Visual Programming Languages For Implementing Computational Design Concepts:A Comparison From A Pedagogical Point Of View Gabriela Celani and Carlos Eduardo Verzola Vaz Abstract This paper compares the use of scripting languages and visual programming languages for teaching computational design concepts to novice and advanced architecture students. Both systems are described and discussed in terms of the representation methods they use.With novice students better results were obtained with the visual programming language. However, the generative strategies used were restricted to parametric variation and the use of randomness. Scripting, on the other hand, was used by advanced students to implement rule- based generative systems. It is possible to conclude that visual languages can be very useful for making architecture students understand general programming concepts, but scripting languages are fundamental for implementing generative design systems.The paper also discusses the importance of the ability to shift between different representation methods, from more concrete to more abstract, as part of the architectural education. 122 1. INTRODUCTION The insertion of new technologies in architectural education has been the target of many discussions and publications, and the theme of many conferences, especially in the 1980’s and 1990’s, when computers became accessible for most architecture schools.The central issue in these discussions has progressively evolved from the introduction of software packages with simple representation purposes, to those with more complex analytical purposes, and finally to those which could be truly integrated in the design process, allowing automated form generation and exploration [1].
    [Show full text]