DOCSLIB.ORG

Developing Cross-Platform Plugins for Brainvoyager QX

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Developing Cross-Platform Plugins for Brainvoyager QX Developing cross-platform plugins for BrainVoyager QX Hester Breman, Pim Pullens and Joost Mulders Brain Innovation B.V. June 12, 2009 Contents 1 Description 3 1.1 About plugins . 3 1.1.1 Terminology . 3 1.2 General development process . 5 1.2.1 Creating a *.dylib (Mac OS X) . 5 1.2.2 Mixing C and C++ . 5 2 Developing source code 7 2.1 Integrated Development Environments (IDE) . 7 2.1.1 Creating a project in Visual Studio . 8 2.1.2 Creating a project in XCode . 12 2.1.3 Code completion . 12 2.2 Using tools and libraries . 13 2.2.1 Using Numerical Recipes’ code . 13 2.2.2 Using precompiled libraries . 13 2.3 Platform differences . 14 2.3.1 Swapping . 14 2.4 Documentation generation (API) . 15 2.4.1 Windows . 15 2.4.2 Mac OS X . 16 3 Configuration 18 3.1 Introduction . 18 3.2 Changing plugin names . 18 3.2.1 Windows: Visual Studio . 18 3.2.2 Mac OS X: XCode . 19 4 Building the plugin 20 4.1 Windows . 20 4.2 Linux . 20 4.2.1 Using a batch file . 20 5 Debugging 22 5.1 Introduction . 22 5.1.1 Debugging symbols . 22 5.1.2 General problem solving . 22 5.2 Debugging on Windows . 23 5.2.1 Preparation . 23 5.2.2 Setting breakpoints in the code . 24 5.3 Run the BrainVoyager QX plugin while debugging . 26 5.3.1 Starting the debugging . 26 5.3.2 Solving problems . 29 1 5.4 Debugging on Mac OS X . 30 5.4.1 Solving problems . 32 6 Source control 33 6.1 Introduction . 33 6.2 Source control on Windows . 33 6.3 Source control on Mac OS X . 33 6.4 Source control on Linux . 33 A Document history 35 2 Chapter 1 Description 1.1 About plugins It is possible to add your own functionality in C++ code to BrainVoyager QX [1] via the plugin mechanism. The code is added to the execute() function of the *.cpp file (derived from a template file that should be used in order to get the plugin working) and possibly additional files in case the execute() function becomes too large. Also, BrainVoyager QX plugin access header files are provided (via the ’Download’ section of the BrainVoyager website http://www.brainvoyager.com/). These header files contain file format and function definitions. The header files are updated regularly, so take care to use the proper version for your BrainVoyager program. 1.1.1 Terminology The following information about plugins was obtained from information provided online by Microsoft. A dynamic-link library (DLL) is an executable file that acts as a shared library of functions. Dynamic linking provides a way for a process to call a function that is not part of its executable code. The executable code for the function is located in a DLL, which contains one or more functions that are compiled, linked, and stored separately from the processes that use them. DLLs also facilitate the sharing of data and resources. Multiple applications can simultaneously access the contents of a single copy of a DLL in memory. Dynamic linking differs from static linking in that it allows an exe- cutable module (either a .dll or .exe file) to include only the information needed at run time to locate the executable code for a DLL function. In static linking, the linker gets all of the referenced functions from the static link library and places it with your code into your executable. Using dynamic linking instead of static linking offers several advan- tages. DLLs save memory, reduce swapping, save disk space, upgrade easier, provide after-market support, provide a mechanism to extend the MFC [Microsoft Foundation Classes, HB] library classes, support multilanguage programs, and ease the creation of international ver- sions. The following definitions were obtained from Apple documentation. Executable: Executables are standalone binaries and cannot be linked. 3 Dynamic Library: Dynamic libraries are linked at build time and loaded automat- ically when needed. Bundle: Bundle libraries are loaded explicitly at run time (Mac OS X only). Static Library: Static libraries are linked at build time and loaded at execution time. Relocatable Object File: Object files are single-module files which are linked at build time. 4 1.2 General development process 1.2.1 Creating a *.dylib (Mac OS X) The process to create a dynamic library (*.dylib) for Mac OS X is depicted in figure 1.1. Figure 1.1: Creating a dynamic library (*.dylib) on Mac OS X 1.2.2 Mixing C and C++ When using C++ concepts in your C code, including only the headers, for example <map>, <string> and <iterator> might not suffice to get the code working. One needs to declare using the namespace “standard” (see figure ??). 5 Figure 1.2: When mixing C++ with your C code, it can be necessary to add ‘using namespace std;’ 6 Chapter 2 Developing source code In this chapter are some suggestions provided that might be useful when coding a plugin for BrainVoyager QX. 2.1 Integrated Development Environments (IDE) Although some programmers prefer to developer their code in a text editor like vi or code editor, and compile the code with a Makefile, it is also possible to use a code development environment that provides editing and compiling functionality. This is called a integrated development environment (IDE). A well-known IDE for Windows is from Microsoft: Visual Studio. Apple provides the IDE XCode. For Linux KDevelop is available. This uses an external compiler, for example the GNU compiler gcc. Cross-platforms alternatives are Code::Blocks (see http://www.codeblocks.org/) and Qt Creator (see http://www.qtsoftware.com/downloads/). Thanks to Michele Rodaro for the Code::Blocks recommendation. 7 2.1.1 Creating a project in Visual Studio When creating a plugin for BrainVoyager QX, one always needs the BrainVoyager Plugin Access functions and the file format files (for example Plugin_VMR_Header.h). Therefore, in Visual Studio, we can start a new project from existing files (see figure 2.1). Figure 2.1: Step 1 in Visual Studio 8 Select the C++ language (see figure 2.2). Figure 2.2: Step 2 in Visual Studio 9 Select the directory where the BrainVoyager Plugin Access header files are lo- cated. The Visual Studio project will be created in this folder as well (see figure 2.3). Figure 2.3: Step 3 in Visual Studio 10 Select the Dynamic Library type of project (see figure 2.4). Figure 2.4: Step 4 in Visual Studio 11 2.1.2 Creating a project in XCode 2.1.3 Code completion In XCode on Mac OS X, code completion can be performed by CodeSense. Go to the ‘Preferences’ tab of XCode to enable CodeSense. On Windows, you will need an additional tool for Visual Studio to perform autocompletion; the WholeTomato software is well recommended. 12 2.2 Using tools and libraries 2.2.1 Using Numerical Recipes’ code The numerical recipes from Vetterling et al [2] can be used successfully if 1. the function files (*.c or *.cpp) are embedded in the XCode or Visual Studio project; in case of *.c files, the files might need to be renamed to *.cpp 2. the project settings are thus modified that the headers of the numerical recipes functions can be found 3. when using the data structures, take care of the indexing of matrices and arrays (1...n) instead of (0...n-1). 2.2.2 Using precompiled libraries The following section can be relevant when using pre-compiled (scientific) libraries. 1. Copy the *.lib file into C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\Lib. In Visual Studio, set the properties of your project as follows: 2. Properties ! Linker ! Input ! additional dependencies ! select the *.lib file. 3. Properties ! General ! Additional Include directories ! add the directories where other files of the library are located. 4. Copy the *.dll file(s) into the output directory of your project (ie the place where your nice exe or dll lives). 13 2.3 Platform differences 2.3.1 Swapping Some machines are still big endian, which causes a shuffling of the bytes in each multi-byte data type like short, float, integer and double. An example is the Apple PowerPC. To adapt the data handling to the routines, the headers CFByteOrder.h of the CoreFoundation classes or NS....h of the Cocoa classes can be used. Apple developed a mechanism called universal binary, which runs on both Pow- erPC and Intel Mac machines. When the dynamic library was originally developed for PowerPC but is used on Intel Mac, the translation system “Rosetta” is used to provide necessary adaptations of the plugin. 14 2.4 Documentation generation (API) When other people are going to use the functions, or just for later, it might be use- ful to write above each function a short explanation of the input parameters, the output values and the goal of the function. If these explanations are written with some attention for the format, they can be automatically collected in a document or HTML pages and resemble the interface to your functions, e.g. an Application Programmer’s Interface (API). Some open-source tools can be downloaded from SourceForge.net, like doxygen or doc++. Others are included in the integrated development environments (IDEs) like HeaderDoc in XCode on Mac OS X. The documentation generation usually consists of two steps. In the first step, all documentation fragments are collected; in doc++ for example, this process is called “docify”. Secondly, the documentation is generated from the collected frag- ments; in doc++, this is called “docxx”.
Load more

Recommended publications
  • Doxydoxygen User Guide Release 0.79.4
    DoxyDoxygen User Guide Release 0.79.4 20Tauri Aug 16, 2021 MANUAL 1 Welcome to DoxyDoxygen 1 2 Installation 3 2.1 Software installation with Package Control...............................3 2.2 Manual software installation.......................................3 2.3 License installation............................................4 2.4 EULA (End User License Agreement)..................................4 2.4.1 Licenses.............................................4 2.4.2 Description of other rights and limitations...........................4 2.4.3 No warranties..........................................5 3 Usage 7 3.1 Create a documentation block......................................7 3.2 Update / wrap an existing documentation block.............................8 3.3 Switch between comment styles.....................................9 3.4 Extend a documentation block......................................9 3.4.1 Auto-completion........................................9 3.4.2 Comment continuation..................................... 10 3.5 Navigate in documentation........................................ 10 3.5.1 Move to the right column.................................... 10 3.5.2 Follow references........................................ 10 3.6 Fold / Unfold comments......................................... 11 3.7 Translate................................................. 11 3.8 Generate documentation......................................... 12 4 Customization 13 4.1 Settings.................................................. 13 4.1.1 Understand
    [Show full text]
  • Use of the Protocol Generator
    Manual for the protocol generator Table of contents Manual for the protocol generator.....................................................................................................................1 Introduction..................................................................................................................................................3 Acknowledgements.......................................................................................................................................................3 Preparation and installation..........................................................................................................................4 Preparation for Presentation *.log file before acquiring data........................................................................................4 Installation......................................................................................................................................................................5 Using the protocol generator........................................................................................................................6 Activating the plugin......................................................................................................................................................6 Main menu.....................................................................................................................................................................7 Option 1: generating a protocol file..............................................................................................................8
    [Show full text]
  • Headerdoc Unfettered
    HeaderDoc Unfettered May 27, 2004 CDB is a trademark of Third Eye Software, Apple Computer, Inc. Inc. © 1999, 2004 Apple Computer, Inc. Helvetica is a trademark of Heidelberger All rights reserved. Druckmaschinen AG, available from Linotype Library GmbH. No part of this publication may be reproduced, stored in a retrieval system, or Java and all Java-based trademarks are transmitted, in any form or by any means, trademarks or registered trademarks of Sun mechanical, electronic, photocopying, Microsystems, Inc. in the U.S. and other recording, or otherwise, without prior countries. written permission of Apple Computer, Inc., Simultaneously published in the United with the following exceptions: Any person States and Canada. is hereby authorized to store documentation Even though Apple has reviewed this manual, on a single computer for personal use only APPLE MAKES NO WARRANTY OR and to print copies of documentation for REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS MANUAL, personal use provided that the ITS QUALITY, ACCURACY, documentation contains Apple's copyright MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. AS A RESULT, THIS notice. MANUAL IS SOLD ªAS IS,º AND YOU, THE PURCHASER, ARE ASSUMING THE ENTIRE The Apple logo is a trademark of Apple RISK AS TO ITS QUALITY AND ACCURACY. Computer, Inc. IN NO EVENT WILL APPLE BE LIABLE FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, Use of the ªkeyboardº Apple logo OR CONSEQUENTIAL DAMAGES (Option-Shift-K) for commercial purposes RESULTING FROM ANY DEFECT OR without the prior written consent of Apple INACCURACY IN THIS MANUAL, even if advised of the possibility of such damages.
    [Show full text]
  • Comments and Documentation 2501ICT/7421Ictnathan
    C Comments Using Doxygen Comments and Documentation 2501ICT/7421ICTNathan René Hexel School of Information and Communication Technology Griffith University Semester 1, 2012 René Hexel Comments and Documentation C Comments Using Doxygen Outline 1 C Comments 2 Using Doxygen René Hexel Comments and Documentation C Comments Using Doxygen Comments Plain C allows comments between /* and */ /* this is a valid C comment */ Comments may not be nested /* this /* is not a valid C comment */ */ C99 also allows double-slash // end-of-line comments // this is a valid comment no closing sequence needed – the comment ends at the end of the line René Hexel Comments and Documentation C Comments Using Doxygen Comment Example Example (Program with Comments) /* * This program prints "j = 007". * It does not take any parameters and returns 0 on success. */ int main(void)/ * main function definition */ { int j; // our int variable to play with j=7; // assign a value to be printed printf("j = %03.3dnn",j); // print value with leading zeroes return 0; // everything is fine, exit program } René Hexel Comments and Documentation C Comments Using Doxygen Where to put comments? At the beginning of each file (module) describe the name of the module, purpose, author, and dates when first created and last modified Before each function (method) describe the purpose of the function or method, input parameters (arguments), return values (output parameters), and pre- and postconditions (contract) At the beginning of each class describe the purpose of the class, and things to
    [Show full text]
  • Nateguyver Breakpoints LLDB Debug Toolchain More
    ��������������������������� ��������������������������� �������� ����������������������������������������������������������������������������������� ���������������������������������������������������������������������������������������������� ������������������������������������������������������������������������������������������� ������������������������������� ��������������������������������������������������������������������������������������� ����������������������������������������������������������������������� �������������������������������������������������������������������������������������� �������������������������������������������� ◼ Breakpoints & watchpoints ◼ Xcode's graphical debugger ◼ LLDB �������������� “ ������������������������������������������������������������������������������������ ��������������������������� ”������������������ ���������������������������� ◼ Assertions, Logging, and Debug configuration ◼ Static analysis & runtime memory tools ◼ Unit testing in xcode ���������������� ◼ Emphasis on LLDB as our debugging foundation ◼ Tips and tricks to stramline your the debuggin experience ◼ Use LLDB as an extensible investigative tool “�������������”������������ “��’���������������������������������������������������’���������������������’�������������� ��������’����������������������������������� ”������������������ ��������������������������������������������������� ���������������������������������������������������������������������������������� ����������������������������������������������������������������������������
    [Show full text]
  • Session 402 Evan Cheng Sr
    What's New in the LLVM Compiler Session 402 Evan Cheng Sr. Manager, Compilation Technologies These are confidential sessions—please refrain from streaming, blogging, or taking pictures Focused on Providing Best-in-Class Tools Focused on Providing Best-in-Class Tools Support for latest hardware Focused on Providing Best-in-Class Tools Support for latest hardware Improving performance Focused on Providing Best-in-Class Tools Support for latest hardware Improving performance Improving developer productivity Support for Latest Hardware armv7s Architecture • Architecture for Apple A6 processor ■ iPhone 5 and new iPads • Extensive tuning and optimization in the compiler ■ Uses instructions only available in armv7s armv7s Architecture • Architecture for Apple A6 processor ■ iPhone 5 and new iPads • Extensive tuning and optimization in the compiler ■ Uses instructions only available in armv7s Important for achieving max performance! armv7s Architecture • Already part of the standard architectures for iOS apps Intel AVX • 256-bit floating-point vector computation ■ Twice as wide as SSE vectors ■ Supported in Sandy Bridge and Ivy Bridge processors • Good for loops with operations that can be performed in parallel ■ Floating-point intensive ■ High ratio of computation to memory bandwidth Intel AVX2 • Supported in “Haswell” processors ■ Extend the AVX instruction set to integers ■ Adds fused multiply-accumulate for increased floating point throughput ■ More extensive set of vector shuffle instructions Using AVX2 with Fallback to AVX / SSE • Check
    [Show full text]
  • Darwin: Mac OS X's Core OS
    ADC April 2001 3/8/01 1:57 PM Page 1 Apple Developer Connection Direct Darwin: Mac OS X’s Core OS eneath Mac OS X’s user-friendly and attractive user interface, Most of the reference documents can be Aqua, and the application frameworks (Classic, Carbon and found in the /Developer/Documentation/ BCocoa) is Darwin: Mac OS X’s core OS. Unseen by users, Kernel directory on any Mac OS X system Darwin provides a strong yet flexible foundation with features like with the Mac OS X Developer Tools package preemptive multitasking, protected memory and real-time support installed. that make Mac OS X a truly modern operating system. The focus of this article is to provide a brief overview of Components of Darwin Darwin and its components as well as give an introduction to Just like in the old Reese’s Peanut Butter developing kernel extensions—modules that extend Darwin’s Cups commercials (“You’ve got chocolate in functionality. For more in-depth information, you should read my peanut butter… No, you’ve got peanut butter on my choco- Inside Mac OS X: Kernel Environment which is available, along late!”), Darwin blends a mixture of mature industry standard com- with other documents referred to in this article, on the Apple ponents such as Mach and BSD with Apple-engineered components Developer Connection (ADC) web site in the Mac OS X to provide Mac OS X with a stable, reliable and extensible founda- Documentation section: tion. Darwin consists of five main components: Mach, I/O Kit, File http://developer.apple.com/techpubs/macosx/macosx.html System, Networking and BSD.
    [Show full text]
  • Mac OS X Server
    Mac OS X Server Version 10.4 Technology Overview August 2006 Technology Overview 2 Mac OS X Server Contents Page 3 Introduction Page 5 New in Version 10.4 Page 7 Operating System Fundamentals UNIX-Based Foundation 64-Bit Computing Advanced BSD Networking Architecture Robust Security Directory Integration High Availability Page 10 Integrated Management Tools Server Admin Workgroup Manager Page 14 Service Deployment and Administration Open Directory Server File and Print Services Mail Services Web Hosting Enterprise Applications Media Streaming iChat Server Software Update Server NetBoot and NetInstall Networking and VPN Distributed Computing Page 29 Product Details Page 31 Open Source Projects Page 35 Additional Resources Technology Overview 3 Mac OS X Server Introduction Mac OS X Server version 10.4 Tiger gives you everything you need to manage servers in a mixed-platform environment and to con gure, deploy, and manage powerful network services. Featuring the renowned Mac OS X interface, Mac OS X Server streamlines your management tasks with applications and utilities that are robust yet easy to use. Apple’s award-winning server software brings people and data together in innovative ways. Whether you want to empower users with instant messaging and blogging, gain greater control over email, reduce the cost and hassle of updating software, or build your own distributed supercomputer, Mac OS X Server v10.4 has the tools you need. The Universal release of Mac OS X Server runs on both Intel- and PowerPC-based The power and simplicity of Mac OS X Server are a re ection of Apple’s operating sys- Mac desktop and Xserve systems.
    [Show full text]
  • Mac OS X Technology Overview
    Mac OS X Technology Overview 2006-06-28 Finder, Safari, Spotlight, Tiger, and Xserve Apple Inc. are trademarks of Apple Inc. © 2004, 2006 Apple Computer, Inc. Adobe, Acrobat, and PostScript are All rights reserved. trademarks or registered trademarks of Adobe Systems Incorporated in the U.S. No part of this publication may be and/or other countries. reproduced, stored in a retrieval system, or transmitted, in any form or by any means, Intel and Intel Core are registered mechanical, electronic, photocopying, trademarks of Intel Corportation or its recording, or otherwise, without prior subsidiaries in the United States and other written permission of Apple Inc., with the countries. following exceptions: Any person is hereby Java and all Java-based trademarks are authorized to store documentation on a trademarks or registered trademarks of Sun single computer for personal use only and Microsystems, Inc. in the U.S. and other to print copies of documentation for countries. personal use provided that the OpenGL is a registered trademark of Silicon documentation contains Apple’s copyright Graphics, Inc. notice. PowerPC and and the PowerPC logo are The Apple logo is a trademark of Apple Inc. trademarks of International Business Use of the “keyboard” Apple logo Machines Corporation, used under license (Option-Shift-K) for commercial purposes therefrom. without the prior written consent of Apple UNIX is a registered trademark of The Open may constitute trademark infringement and Group unfair competition in violation of federal and state laws. Simultaneously published in the United States and Canada. No licenses, express or implied, are granted with respect to any of the technology Even though Apple has reviewed this document, APPLE MAKES NO WARRANTY OR described in this document.
    [Show full text]
  • Mac OS X Server Introduction to Command-Line Administration Version 10.6 Snow Leopard Kkapple Inc
    Mac OS X Server Introduction to Command-Line Administration Version 10.6 Snow Leopard K Apple Inc. Apple Remote Desktop, Finder, and Snow Leopard are © 2009 Apple Inc. All rights reserved. trademarks of Apple Inc. Under the copyright laws, this manual may not AIX is a trademark of IBM Corp., registered in the U.S. be copied, in whole or in part, without the written and other countries, and is being used under license. consent of Apple. The Bluetooth® word mark and logos are registered The Apple logo is a trademark of Apple Inc., registered trademarks owned by Bluetooth SIG, Inc. and any use in the U.S. and other countries. Use of the “keyboard” of such marks by Apple is under license. Apple logo (Option-Shift-K) for commercial purposes without the prior written consent of Apple may This product includes software developed by the constitute trademark infringement and unfair University of California, Berkeley, FreeBSD, Inc., competition in violation of federal and state laws. The NetBSD Foundation, Inc., and their respective contributors. Every effort has been made to ensure that the information in this manual is accurate. Apple is not Java™ and all Java-based trademarks and logos responsible for printing or clerical errors. are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Apple 1 Infinite Loop PowerPC™ and the PowerPC logo™ are trademarks Cupertino, CA 95014 of International Business Machines Corporation, used 408-996-1010 under license therefrom. www.apple.com UNIX® is a registered trademark of The Open Group. Apple, the Apple logo, AppleScript, FireWire, Keychain, Other company and product names mentioned herein Leopard, Mac, Mac OS, Quartz, Safari, Xcode, Xgrid, and are trademarks of their respective companies.
    [Show full text]
  • Developer Guide: Ios Native Applications Sybase Unwired Platform 2.1 DOCUMENT ID: DC01217-01-0210-03 LAST REVISED: July 2012 Copyright © 2012 by Sybase, Inc
    Developer Guide: iOS Native Applications Sybase Unwired Platform 2.1 DOCUMENT ID: DC01217-01-0210-03 LAST REVISED: July 2012 Copyright © 2012 by Sybase, Inc. All rights reserved. This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. Upgrades are provided only at regularly scheduled software release dates. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Sybase, Inc. Sybase trademarks can be viewed at the Sybase trademarks page at http://www.sybase.com/detail?id=1011207. Sybase and the marks listed are trademarks of Sybase, Inc. ® indicates registration in the United States of America. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Java and all Java-based marks are trademarks or registered trademarks of Oracle and/or its affiliates in the U.S. and other countries. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. All other company and product names mentioned may be trademarks of the respective companies with which they are associated. Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies.
    [Show full text]
  • Introduction to Objective-C 2501ICT/7421ICT Nathan
    Objective-C Classes Compiling Objective-C Code Introduction to Objective-C 2501ICT/7421ICT Nathan René Hexel School of Information and Communication Technology Griffith University Semester 1, 2012 René Hexel Introduction to Objective-C Objective-C Classes Compiling Objective-C Code Outline 1 Objective-C Classes Objective-C 2 Compiling Objective-C Code Compiling and Makefiles Documentation with HeaderDoc René Hexel Introduction to Objective-C Objective-C Classes Objective-C Compiling Objective-C Code Classes and Objects in Objective-C So far: Pure C procedural, no object-oriented concepts difficult to write re-usable code: disadvantage for larger projects Objective-C is a small syntax addition to C highly dynamic and very powerful object model classes are first class objects ! most features implemented through methods René Hexel Introduction to Objective-C Objective-C Classes Objective-C Compiling Objective-C Code A Point Class Interface Java: Point.java Objective-C: Point.h import java.lang.System; #import <Foundation/Foundation.h> class Point extends Object @interface Point: NSObject { { int x; int x; // member variables int y; int y; // protected by default } public Point() {x=0;y=0;} - init; // constructor public int getX() { return x;} -(int)x; // access methods public void setX(int newx) -(void) setX:(int) newx; {x= newx;} } @end René Hexel Introduction to Objective-C Objective-C Classes Objective-C Compiling Objective-C Code A Point Class Implementation Java: Point.java Objective-C: Point.m import java.lang.System; #import "Point.h"
    [Show full text]