 Programmer’s Guide for Free Pascal, Version 3.2.22.2 Exporting variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 7.2.3 Compiling libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 7.2.4 Unit searching E.8.6 Informative rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 F Compiling the compiler 175 F.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 F.3 Compiling using make . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 F.3.1 Basic compilation0 码力 | 187 页 | 531.58 KB | 1 年前3 Programmer’s Guide for Free Pascal, Version 3.2.22.2 Exporting variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 7.2.3 Compiling libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 7.2.4 Unit searching E.8.6 Informative rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 F Compiling the compiler 175 F.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 F.3 Compiling using make . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 F.3.1 Basic compilation0 码力 | 187 页 | 531.58 KB | 1 年前3
 User’s Guide for Free Pascal, Version 3.2.2configuration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.4 Before compiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.5 Testing the compiler . . . . . . . . . . . . . . . . . . . 21 3.2 Compiling a program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.3 Compiling a unit . . . . . . . . . . . . . . . . . . . . 5 Reducing the size of your program . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 4 Compiling problems 23 4.1 General problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 码力 | 217 页 | 756.57 KB | 1 年前3 User’s Guide for Free Pascal, Version 3.2.2configuration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.4 Before compiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.5 Testing the compiler . . . . . . . . . . . . . . . . . . . 21 3.2 Compiling a program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.3 Compiling a unit . . . . . . . . . . . . . . . . . . . . 5 Reducing the size of your program . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 4 Compiling problems 23 4.1 General problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 码力 | 217 页 | 756.57 KB | 1 年前3
 The Rust Programming Language,2nd Editionex- pression is over, and the next one is ready to begin. Most lines of Rust code end with a ;. Compiling and Running Are Separate Steps In “Writing and Running a Rust Program”, we showed you how to run you come from a C or C++ background, you’ll notice that this is similar to gcc or clang. After compiling successfully, Rust should output a binary executable, which you can see on Linux or OSX by entering terminal. If you come from a dynamic language like Ruby, Python, or JavaScript, you may not be used to compiling and running a program being sep- arate steps. Rust is an ahead-of-time compiled language, which0 码力 | 617 页 | 1.54 MB | 1 年前3 The Rust Programming Language,2nd Editionex- pression is over, and the next one is ready to begin. Most lines of Rust code end with a ;. Compiling and Running Are Separate Steps In “Writing and Running a Rust Program”, we showed you how to run you come from a C or C++ background, you’ll notice that this is similar to gcc or clang. After compiling successfully, Rust should output a binary executable, which you can see on Linux or OSX by entering terminal. If you come from a dynamic language like Ruby, Python, or JavaScript, you may not be used to compiling and running a program being sep- arate steps. Rust is an ahead-of-time compiled language, which0 码力 | 617 页 | 1.54 MB | 1 年前3
 Angular CLI Tutorial\>Node\>TutorialsPoint> ng build Compiling @angular/animations : es2015 as esm2015 Compiling @angular/core : es2015 as esm2015 Compiling @angular/compiler/testing : es2015 as esm2015 Compiling @angular/animations/browser es2015 as esm2015 Compiling @angular/core/testing : es2015 as esm2015 Compiling @angular/common : es2015 as esm2015 Compiling @angular/platform-browser : es2015 as esm2015 Compiling @angular/common/http @angular/common/http : es2015 as esm2015 Compiling @angular/common/testing : es2015 as esm2015 Compiling @angular/platform-browser-dynamic : es2015 as esm2015 Compiling @angular/platform-browser/testing : es20150 码力 | 64 页 | 1.04 MB | 1 年前3 Angular CLI Tutorial\>Node\>TutorialsPoint> ng build Compiling @angular/animations : es2015 as esm2015 Compiling @angular/core : es2015 as esm2015 Compiling @angular/compiler/testing : es2015 as esm2015 Compiling @angular/animations/browser es2015 as esm2015 Compiling @angular/core/testing : es2015 as esm2015 Compiling @angular/common : es2015 as esm2015 Compiling @angular/platform-browser : es2015 as esm2015 Compiling @angular/common/http @angular/common/http : es2015 as esm2015 Compiling @angular/common/testing : es2015 as esm2015 Compiling @angular/platform-browser-dynamic : es2015 as esm2015 Compiling @angular/platform-browser/testing : es20150 码力 | 64 页 | 1.04 MB | 1 年前3
 Just-in-Time Compilation - J F Bastien - CppCon 2020primitives than even what a CISC processor does. JiTs can benefit from this size saving by only compiling the code that matters, and leaving the rest in a compressed form.3. Interpreted programs tend to word…Java “Java” That’s right, I said it, at a C++ conference…Java At least I didn’t say “Rust”…Compiling Java just in time Avoiding unnecessary overhead is crucial for fast compilation. In many compilers compilers, constructing an intermediate representation (IR) of a method is a standard process. When compiling from Java bytecode, however, we can eliminate that overhead. The bytecodes themselves are an IR0 码力 | 111 页 | 3.98 MB | 6 月前3 Just-in-Time Compilation - J F Bastien - CppCon 2020primitives than even what a CISC processor does. JiTs can benefit from this size saving by only compiling the code that matters, and leaving the rest in a compressed form.3. Interpreted programs tend to word…Java “Java” That’s right, I said it, at a C++ conference…Java At least I didn’t say “Rust”…Compiling Java just in time Avoiding unnecessary overhead is crucial for fast compilation. In many compilers compilers, constructing an intermediate representation (IR) of a method is a standard process. When compiling from Java bytecode, however, we can eliminate that overhead. The bytecodes themselves are an IR0 码力 | 111 页 | 3.98 MB | 6 月前3
 Coroutines in	KotlinMotivation/Examples • Solutions in other languages • Kotlin’s Solution – Client code – Library code • Compiling Coroutines • Exception Handling • Appendix. Serializable Coroutines? “Legal” • All I’m saying suspend fun yield(value: T, c: Continuation Coroutines in	KotlinMotivation/Examples • Solutions in other languages • Kotlin’s Solution – Client code – Library code • Compiling Coroutines • Exception Handling • Appendix. Serializable Coroutines? “Legal” • All I’m saying suspend fun yield(value: T, c: Continuation- ) { setNext(value) setNextStep(c) } ... } Compiling to State Machines generate { var cur = 1 var next = 1 yield(1) while (true) { yield(next) next = 1 yield(1) while (true) { yield(next) val tmp = cur + next cur = next next = tmp } } Compiling Coroutines (I) class fibonacci$1 implements Function1, Continuation { private GeneratorController 0 码力 | 39 页 | 1.01 MB | 1 年前3
 The Go frontend for GCCconverted to GENERIC. I describe the structure of the frontend and the IR, issues that arise when compiling the Go language, and issues with hook- ing up any frontend to the gcc middle-end. 1 Introduction be static to this package. So gccgo must build all such tables here, in case it needs them when compiling some other package. 12. Gccgo walks the IR looking for all uses of && and || and converts them package name, the name of the initial- ization function, and the package priority. This is used when compiling the main package to call all required initialization routines. The list is inclu- sive, in that0 码力 | 14 页 | 122.25 KB | 1 年前3 The Go frontend for GCCconverted to GENERIC. I describe the structure of the frontend and the IR, issues that arise when compiling the Go language, and issues with hook- ing up any frontend to the gcc middle-end. 1 Introduction be static to this package. So gccgo must build all such tables here, in case it needs them when compiling some other package. 12. Gccgo walks the IR looking for all uses of && and || and converts them package name, the name of the initial- ization function, and the package priority. This is used when compiling the main package to call all required initialization routines. The list is inclu- sive, in that0 码力 | 14 页 | 122.25 KB | 1 年前3
 The Gimp User’s Manual version 1.0.1761 Tables 764 Chapter 47: Compiling Plug-ins................................... 769 Compile 770 How To Obtain And Install The Source Code 771 Compiling The Code 771 PART XI Appendixes will learn more about plug-ins in Chapters 23 through 39, and in “Compiling Plug-ins” on page 769, we provide a few tips on compiling plug-ins. • The scripts subdirectory holds any personal Script-Fus build your Gimp application. (If you’re having problems, you will find more information on compiling in “Compiling Plug-ins” on page 769.) If there were no errors, Gimp built successfully, and you can install0 码力 | 924 页 | 9.50 MB | 1 年前3 The Gimp User’s Manual version 1.0.1761 Tables 764 Chapter 47: Compiling Plug-ins................................... 769 Compile 770 How To Obtain And Install The Source Code 771 Compiling The Code 771 PART XI Appendixes will learn more about plug-ins in Chapters 23 through 39, and in “Compiling Plug-ins” on page 769, we provide a few tips on compiling plug-ins. • The scripts subdirectory holds any personal Script-Fus build your Gimp application. (If you’re having problems, you will find more information on compiling in “Compiling Plug-ins” on page 769.) If there were no errors, Gimp built successfully, and you can install0 码力 | 924 页 | 9.50 MB | 1 年前3
 Reference manual for FPDoc Document version 3.2.2information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2 Compiling and Installing FPDOC 7 2.1 Compiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . please do not hesitate and contact me at michael@freepascal.org. 6 Chapter 2 Compiling and Installing FPDOC 2.1 Compiling In order to compile FPDOC, the following things are needed: 1. The fpdoc sources Installation When installing from sources, a simple make install cd intl make install 7 CHAPTER 2. COMPILING AND INSTALLING FPDOC should completely install the documentation tool. When installing from a0 码力 | 47 页 | 196.25 KB | 1 年前3 Reference manual for FPDoc Document version 3.2.2information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2 Compiling and Installing FPDOC 7 2.1 Compiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . please do not hesitate and contact me at michael@freepascal.org. 6 Chapter 2 Compiling and Installing FPDOC 2.1 Compiling In order to compile FPDOC, the following things are needed: 1. The fpdoc sources Installation When installing from sources, a simple make install cd intl make install 7 CHAPTER 2. COMPILING AND INSTALLING FPDOC should completely install the documentation tool. When installing from a0 码力 | 47 页 | 196.25 KB | 1 年前3
 ThinkJS 2.1 Documentationcode to handle them with async/await . Last, it can run in Node.js environment stably after Babel compiling. TypeScript is an free and open source programming language designed by Microsoft. TypeScript is and run npm install to install dependencies. Since v2.0.6, ThinkJS has built-in the automatical compiling feature, so you don’t need run npm run watch-compile for real time compile anymore. What you only has changed. Change Thinkjs’s version to 2.1.x in package.json. ThinkJS has used Babel 5 for compiling, and now it has updated to 6 in the ThinkJS 2.1, so we need to modify Babel’s version. You can0 码力 | 148 页 | 1.69 MB | 1 年前3 ThinkJS 2.1 Documentationcode to handle them with async/await . Last, it can run in Node.js environment stably after Babel compiling. TypeScript is an free and open source programming language designed by Microsoft. TypeScript is and run npm install to install dependencies. Since v2.0.6, ThinkJS has built-in the automatical compiling feature, so you don’t need run npm run watch-compile for real time compile anymore. What you only has changed. Change Thinkjs’s version to 2.1.x in package.json. ThinkJS has used Babel 5 for compiling, and now it has updated to 6 in the ThinkJS 2.1, so we need to modify Babel’s version. You can0 码力 | 148 页 | 1.69 MB | 1 年前3
共 1000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 100














 
 