. . . . . . . . . . . . . . . . 127 13 方法 129 13.1 定义方法 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 13.2 方法歧义 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 13.3 参数方法 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 13.4 重定义方法 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 13.5 使用参数方法设计样式 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 从超类型中提取出类型参数 . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . 414 How do I check if the current file is being run as the main script? . . . . . . . . . . . . . . . . . . . 414 How do I catch CTRL-C in a script? . . . . . . . . . 1151 103Documenta�on of Julia’s Internals 1153 103.1Ini�aliza�on of the Julia run�me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153 main() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1200 103.15prin�() and stdio in the Julia run�me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1203 Libuv wrappers for stdio

. . . . . . . . . . . . . . . . . . . . . . . . 416 How do I check if the current file is being run as the main script? . . . . . . . . . . . . . . . . . . . 416 How do I catch CTRL-C in a script? . . . . . . . . . 1153 104Documenta�on of Julia’s Internals 1155 104.1Ini�aliza�on of the Julia run�me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155 main() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1202 104.15prin�() and stdio in the Julia run�me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205 Libuv wrappers for stdio

. . . . . . . . . . . . . . . . . . . . . . . . 408 How do I check if the current file is being run as the main script? . . . . . . . . . . . . . . . . . . . 408 How do I catch CTRL-C in a script? . . . . . . . . . 1117 101Documenta�on of Julia’s Internals 1119 101.1Ini�aliza�on of the Julia run�me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119 main() . . . . . . . . . . . . . . . . . . . . . . . . 1166 xviii CONTENTS 101.15prin�() and stdio in the Julia run�me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169 Libuv wrappers for stdio

. . . . . . . . . . . . . . . . . . . . . . . . 406 How do I check if the current file is being run as the main script? . . . . . . . . . . . . . . . . . . . 406 How do I catch CTRL-C in a script? . . . . . . . . . 1115 101Documenta�on of Julia’s Internals 1117 101.1Ini�aliza�on of the Julia run�me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117 main() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164 101.15prin�() and stdio in the Julia run�me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167 Libuv wrappers for stdio

compiler, types exist only at compile time and cannot be manipulated or expressed at run time. In Julia, types are themselves run-time objects, and can also be used to convey information to the compiler. What for the + function. Existing code then seamlessly applies to the new data types. Partly because of run-time type inference (augmented by optional type annotations), and partly because of a strong focus interactive session, type CTRL-D (press the Control/^ key together with the d key), or type exit(). When run in interactive mode, julia displays a banner and prompts the user for input. Once the user has entered

compiler, types exist only at compile time and cannot be manipulated or expressed at run time. In Julia, types are themselves run-time objects, and can also be used to convey information to the compiler. What for the + function. Existing code then seamlessly applies to the new data types. Partly because of run-time type inference (augmented by optional type annotations), and partly because of a strong focus interactive session, type CTRL-D (press the Control/^ key together with the d key), or type exit(). When run in interactive mode, julia displays a banner and prompts the user for input. Once the user has entered

compiler, types exist only at compile time and cannot be manipulated or expressed at run time. In Julia, types are themselves run-time objects, and can also be used to convey information to the compiler. What for the + function. Existing code then seamlessly applies to the new data types. Partly because of run-time type inference (augmented by optional type annotations), and partly because of a strong focus interactive session, type CTRL-D (press the Control/^ key together with the d key), or type exit(). When run in interactive mode, julia displays a banner and prompts the user for input. Once the user has entered

compiler, types exist only at compile time and cannot be manipulated or expressed at run time. In Julia, types are themselves run-time objects, and can also be used to convey information to the compiler. What for the + function. Existing code then seamlessly applies to the new data types. Partly because of run-time type inference (augmented by optional type annotations), and partly because of a strong focus interactive session, type CTRL-D (press the Control/^ key together with the d key), or type exit(). When run in interactive mode, julia displays a banner and prompts the user for input. Once the user has entered

compiler, types exist only at compile time and cannot be manipulated or expressed at run time. In Julia, types are themselves run-time objects, and can also be used to convey information to the compiler. What for the + function. Existing code then seamlessly applies to the new data types. Partly because of run-time type inference (augmented by optional type annotations), and partly because of a strong focus interactive session, type CTRL-D (press the Control/^ key together with the d key), or type exit(). When run in interactive mode, julia displays a banner and prompts the user for input. Once the user has entered