GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — python-docs-ja/extending/newtypes.po at 3.14 · python/python-docs-ja

Expand file tree

/

newtypes.po

Copy path
More file actions
More file actions

Latest commit

 

History

History
History
1472 lines (1354 loc) · 61.7 KB
/

newtypes.po

Copy path

File metadata and controls

1472 lines (1354 loc) · 61.7 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001 Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# python-doc bot, 2025
# Cheesecake, 2025
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.15\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-10-01 19:07+0000\n"
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
"Last-Translator: Cheesecake, 2025\n"
"Language-Team: Japanese (https://app.transifex.com/python-doc/teams/5390/"
"ja/)\n"
"Language: ja\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
#: ../../extending/newtypes.rst:7
msgid "Defining Extension Types: Assorted Topics"
msgstr "拡張の型の定義: 雑多なトピック"
#: ../../extending/newtypes.rst:11
msgid ""
"This section aims to give a quick fly-by on the various type methods you can "
"implement and what they do."
msgstr ""
"この節ではさまざまな実装可能なタイプメソッドと、それらが何をするものであるか"
"について、ざっと説明します。"
#: ../../extending/newtypes.rst:14
msgid ""
"Here is the definition of :c:type:`PyTypeObject`, with some fields only used "
"in :ref:`debug builds <debug-build>` omitted:"
msgstr ""
"以下は :c:type:`PyTypeObject` の定義です。 :ref:`デバッグビルド <debug-"
"build>` でしか使われないいくつかのメンバは省いてあります:"
msgid ""
"typedef struct _typeobject {\n"
" PyObject_VAR_HEAD\n"
" const char *tp_name; /* For printing, in format \"<module>.<name>\" */\n"
" Py_ssize_t tp_basicsize, tp_itemsize; /* For allocation */\n"
"\n"
" /* Methods to implement standard operations */\n"
"\n"
" destructor tp_dealloc;\n"
" Py_ssize_t tp_vectorcall_offset;\n"
" getattrfunc tp_getattr;\n"
" setattrfunc tp_setattr;\n"
" PyAsyncMethods *tp_as_async; /* formerly known as tp_compare (Python 2)\n"
" or tp_reserved (Python 3) */\n"
" reprfunc tp_repr;\n"
"\n"
" /* Method suites for standard classes */\n"
"\n"
" PyNumberMethods *tp_as_number;\n"
" PySequenceMethods *tp_as_sequence;\n"
" PyMappingMethods *tp_as_mapping;\n"
"\n"
" /* More standard operations (here for binary compatibility) */\n"
"\n"
" hashfunc tp_hash;\n"
" ternaryfunc tp_call;\n"
" reprfunc tp_str;\n"
" getattrofunc tp_getattro;\n"
" setattrofunc tp_setattro;\n"
"\n"
" /* Functions to access object as input/output buffer */\n"
" PyBufferProcs *tp_as_buffer;\n"
"\n"
" /* Flags to define presence of optional/expanded features */\n"
" unsigned long tp_flags;\n"
"\n"
" const char *tp_doc; /* Documentation string */\n"
"\n"
" /* Assigned meaning in release 2.0 */\n"
" /* call function for all accessible objects */\n"
" traverseproc tp_traverse;\n"
"\n"
" /* delete references to contained objects */\n"
" inquiry tp_clear;\n"
"\n"
" /* Assigned meaning in release 2.1 */\n"
" /* rich comparisons */\n"
" richcmpfunc tp_richcompare;\n"
"\n"
" /* weak reference enabler */\n"
" Py_ssize_t tp_weaklistoffset;\n"
"\n"
" /* Iterators */\n"
" getiterfunc tp_iter;\n"
" iternextfunc tp_iternext;\n"
"\n"
" /* Attribute descriptor and subclassing stuff */\n"
" PyMethodDef *tp_methods;\n"
" PyMemberDef *tp_members;\n"
" PyGetSetDef *tp_getset;\n"
" // Strong reference on a heap type, borrowed reference on a static type\n"
" PyTypeObject *tp_base;\n"
" PyObject *tp_dict;\n"
" descrgetfunc tp_descr_get;\n"
" descrsetfunc tp_descr_set;\n"
" Py_ssize_t tp_dictoffset;\n"
" initproc tp_init;\n"
" allocfunc tp_alloc;\n"
" newfunc tp_new;\n"
" freefunc tp_free; /* Low-level free-memory routine */\n"
" inquiry tp_is_gc; /* For PyObject_IS_GC */\n"
" PyObject *tp_bases;\n"
" PyObject *tp_mro; /* method resolution order */\n"
" PyObject *tp_cache; /* no longer used */\n"
" void *tp_subclasses; /* for static builtin types this is an index */\n"
" PyObject *tp_weaklist; /* not used for static builtin types */\n"
" destructor tp_del;\n"
"\n"
" /* Type attribute cache version tag. Added in version 2.6.\n"
" * If zero, the cache is invalid and must be initialized.\n"
" */\n"
" unsigned int tp_version_tag;\n"
"\n"
" destructor tp_finalize;\n"
" vectorcallfunc tp_vectorcall;\n"
"\n"
" /* bitset of which type-watchers care about this type */\n"
" unsigned char tp_watched;\n"
"\n"
" /* Number of tp_version_tag values used.\n"
" * Set to _Py_ATTR_CACHE_UNUSED if the attribute cache is\n"
" * disabled for this type (e.g. due to custom MRO entries).\n"
" * Otherwise, limited to MAX_VERSIONS_PER_CLASS (defined elsewhere).\n"
" */\n"
" uint16_t tp_versions_used;\n"
"} PyTypeObject;\n"
msgstr ""
"typedef struct _typeobject {\n"
" PyObject_VAR_HEAD\n"
" const char *tp_name; /* 表示用。形式は \"<module>.<name>\" */\n"
" Py_ssize_t tp_basicsize, tp_itemsize; /* 割り当て用 */\n"
"\n"
" /* 標準の操作を実装するメソッド */\n"
"\n"
" destructor tp_dealloc;\n"
" Py_ssize_t tp_vectorcall_offset;\n"
" getattrfunc tp_getattr;\n"
" setattrfunc tp_setattr;\n"
" PyAsyncMethods *tp_as_async; /* 以前の名前は tp_compare (Python 2)\n"
" または tp_reserved (Python 3) */\n"
" reprfunc tp_repr;\n"
"\n"
" /* 標準クラス用のメソッド群 */\n"
"\n"
" PyNumberMethods *tp_as_number;\n"
" PySequenceMethods *tp_as_sequence;\n"
" PyMappingMethods *tp_as_mapping;\n"
"\n"
" /* その他の標準の操作 (バイナリ互換性のためこの位置に配置) */\n"
"\n"
" hashfunc tp_hash;\n"
" ternaryfunc tp_call;\n"
" reprfunc tp_str;\n"
" getattrofunc tp_getattro;\n"
" setattrofunc tp_setattro;\n"
"\n"
" /* オブジェクトを入出力バッファとして扱う関数 */\n"
" PyBufferProcs *tp_as_buffer;\n"
"\n"
" /* 任意機能や拡張機能の有無を定義するフラグ */\n"
" unsigned long tp_flags;\n"
"\n"
" const char *tp_doc; /* ドキュメント文字列 */\n"
"\n"
" /* リリース 2.0 で意味を割り当て */\n"
" /* アクセス可能な全オブジェクトについて関数を呼び出す */\n"
" traverseproc tp_traverse;\n"
"\n"
" /* 保持するオブジェクトへの参照を削除する */\n"
" inquiry tp_clear;\n"
"\n"
" /* リリース 2.1 で意味を割り当て */\n"
" /* 拡張比較 */\n"
" richcmpfunc tp_richcompare;\n"
"\n"
" /* 弱参照を有効にする */\n"
" Py_ssize_t tp_weaklistoffset;\n"
"\n"
" /* イテレータ */\n"
" getiterfunc tp_iter;\n"
" iternextfunc tp_iternext;\n"
"\n"
" /* 属性デスクリプタとサブクラス化に関するもの */\n"
" PyMethodDef *tp_methods;\n"
" PyMemberDef *tp_members;\n"
" PyGetSetDef *tp_getset;\n"
" // ヒープ型では強参照、静的な型では借用参照\n"
" PyTypeObject *tp_base;\n"
" PyObject *tp_dict;\n"
" descrgetfunc tp_descr_get;\n"
" descrsetfunc tp_descr_set;\n"
" Py_ssize_t tp_dictoffset;\n"
" initproc tp_init;\n"
" allocfunc tp_alloc;\n"
" newfunc tp_new;\n"
" freefunc tp_free; /* 低レベルのメモリ解放ルーチン */\n"
" inquiry tp_is_gc; /* PyObject_IS_GC 用 */\n"
" PyObject *tp_bases;\n"
" PyObject *tp_mro; /* メソッド解決順序 */\n"
" PyObject *tp_cache; /* 現在は未使用 */\n"
" void *tp_subclasses; /* 静的な組み込み型ではインデックス */\n"
" PyObject *tp_weaklist; /* 静的な組み込み型では未使用 */\n"
" destructor tp_del;\n"
"\n"
" /* 型の属性キャッシュのバージョンタグ。バージョン 2.6 で追加。\n"
" * ゼロならキャッシュは無効であり、初期化が必要。\n"
" */\n"
" unsigned int tp_version_tag;\n"
"\n"
" destructor tp_finalize;\n"
" vectorcallfunc tp_vectorcall;\n"
"\n"
" /* この型に関心を持つ型ウォッチャーを表すビット集合 */\n"
" unsigned char tp_watched;\n"
"\n"
" /* 使用された tp_version_tag 値の数。\n"
" * 属性キャッシュがこの型で無効な場合は、\n"
" * _Py_ATTR_CACHE_UNUSED に設定する (独自の MRO エントリーなどによる)。\n"
" * それ以外の場合は MAX_VERSIONS_PER_CLASS (別の場所で定義) 以下。\n"
" */\n"
" uint16_t tp_versions_used;\n"
"} PyTypeObject;\n"
#: ../../extending/newtypes.rst:20
msgid ""
"Now that's a *lot* of methods. Don't worry too much though -- if you have a "
"type you want to define, the chances are very good that you will only "
"implement a handful of these."
msgstr ""
"*たくさんの* メソッドがありますね。でもそんなに心配する必要はありません。定義"
"したい型があるなら、実装するのはこのうちのごくわずかですむことがほとんどで"
"す。"
#: ../../extending/newtypes.rst:24
msgid ""
"As you probably expect by now, we're going to go over this and give more "
"information about the various handlers. We won't go in the order they are "
"defined in the structure, because there is a lot of historical baggage that "
"impacts the ordering of the fields. It's often easiest to find an example "
"that includes the fields you need and then change the values to suit your "
"new type. ::"
msgstr ""
"すでに予想されているでしょうが、この構造体について入念に見ていき、様々なハン"
"ドラについてより詳しい情報を提供します。\n"
"しかしこれらのメンバが構造体中で定義されている順番は無視します。というのは、"
"これらのメンバの現れる順序は歴史的な遺産によるものだからです。\n"
"多くの場合いちばん簡単なのは、必要とするメンバがすべて含まれている例をとって"
"きて、新しく作る型に合わせて値を変更することです。 ::"
msgid "const char *tp_name; /* For printing */"
msgstr "const char *tp_name; /* 表示用 */"
#: ../../extending/newtypes.rst:33
msgid ""
"The name of the type -- as mentioned in the previous chapter, this will "
"appear in various places, almost entirely for diagnostic purposes. Try to "
"choose something that will be helpful in such a situation! ::"
msgstr ""
"これは型の名前です。前の章で説明したように、これは色々な場面で現れ、ほとんど"
"は診断目的で使われるものです。\n"
"それなので、そのような場面で役に立つであろう名前を選んでください! ::"
msgid "Py_ssize_t tp_basicsize, tp_itemsize; /* For allocation */"
msgstr "Py_ssize_t tp_basicsize, tp_itemsize; /* 割り当て用 */"
#: ../../extending/newtypes.rst:39
msgid ""
"These fields tell the runtime how much memory to allocate when new objects "
"of this type are created. Python has some built-in support for variable "
"length structures (think: strings, tuples) which is where "
"the :c:member:`~PyTypeObject.tp_itemsize` field comes in. This will be "
"dealt with later. ::"
msgstr ""
"これらのフィールドは、この型のオブジェクトが新しく作成されるときにどれだけの"
"メモリを割り当てればよいのかをランタイムに指示します。Python には可変長の構造"
"体 (文字列やタプルなどを想像してください) に対する組み込みのサポートがある程"
"度あり、ここで :c:member:`~PyTypeObject.tp_itemsize` メンバが使われます。これ"
"らについてはあとでふれます。 ::"
msgid "const char *tp_doc;"
msgstr "const char *tp_doc;"
msgid ""
"Here you can put a string (or its address) that you want returned when the "
"Python script references ``obj.__doc__`` to retrieve the doc string."
msgstr ""
"ここには、Python スクリプトが ``obj.__doc__`` を参照してドキュメント文字列を"
"取得するときに返す文字列 (またはそのアドレス) を設定します。"
#: ../../extending/newtypes.rst:49
msgid ""
"Now we come to the basic type methods -- the ones most extension types will "
"implement."
msgstr ""
"では次に、型の基本的なメソッドに進みます。ほとんどの拡張の型がこのメソッドを"
"実装します。"
#: ../../extending/newtypes.rst:54
msgid "Finalization and De-allocation"
msgstr "ファイナライズとメモリ解放"
msgid "destructor tp_dealloc;"
msgstr "destructor tp_dealloc;"
#: ../../extending/newtypes.rst:66
msgid ""
"This function is called when the reference count of the instance of your "
"type is reduced to zero and the Python interpreter wants to reclaim it. If "
"your type has memory to free or other clean-up to perform, you can put it "
"here. The object itself needs to be freed here as well. Here is an example "
"of this function::"
msgstr ""
"型のインスタンスの参照カウントがゼロになり、Python インタプリタがそれを潰して"
"再利用したくなると、この関数が呼ばれます。解放すべきメモリをその型が保持して"
"いたり、それ以外にも実行すべき後処理がある場合は、それらをここに入れられま"
"す。オブジェクトそれ自体もここで解放される必要があります。この関数の例は、以"
"下のようなものです::"
msgid ""
"static void\n"
"newdatatype_dealloc(PyObject *op)\n"
"{\n"
" newdatatypeobject *self = (newdatatypeobject *) op;\n"
" free(self->obj_UnderlyingDatatypePtr);\n"
" Py_TYPE(self)->tp_free(self);\n"
"}"
msgstr ""
"static void\n"
"newdatatype_dealloc(PyObject *op)\n"
"{\n"
" newdatatypeobject *self = (newdatatypeobject *) op;\n"
" free(self->obj_UnderlyingDatatypePtr);\n"
" Py_TYPE(self)->tp_free(self);\n"
"}"
msgid ""
"If your type supports garbage collection, the destructor should "
"call :c:func:`PyObject_GC_UnTrack` before clearing any member fields::"
msgstr ""
"型がガベージコレクションをサポートする場合、デストラクタでは、メンバフィール"
"ドをクリアする前に :c:func:`PyObject_GC_UnTrack` を呼び出す必要がありま"
"す。 ::"
msgid ""
"static void\n"
"newdatatype_dealloc(PyObject *op)\n"
"{\n"
" newdatatypeobject *self = (newdatatypeobject *) op;\n"
" PyObject_GC_UnTrack(op);\n"
" Py_CLEAR(self->other_obj);\n"
" ...\n"
" Py_TYPE(self)->tp_free(self);\n"
"}"
msgstr ""
"static void\n"
"newdatatype_dealloc(PyObject *op)\n"
"{\n"
" newdatatypeobject *self = (newdatatypeobject *) op;\n"
" PyObject_GC_UnTrack(op);\n"
" Py_CLEAR(self->other_obj);\n"
" ...\n"
" Py_TYPE(self)->tp_free(self);\n"
"}"
#: ../../extending/newtypes.rst:97
msgid ""
"One important requirement of the deallocator function is that it leaves any "
"pending exceptions alone. This is important since deallocators are "
"frequently called as the interpreter unwinds the Python stack; when the "
"stack is unwound due to an exception (rather than normal returns), nothing "
"is done to protect the deallocators from seeing that an exception has "
"already been set. Any actions which a deallocator performs which may cause "
"additional Python code to be executed may detect that an exception has been "
"set. This can lead to misleading errors from the interpreter. The proper "
"way to protect against this is to save a pending exception before performing "
"the unsafe action, and restoring it when done. This can be done using "
"the :c:func:`PyErr_Fetch` and :c:func:`PyErr_Restore` functions::"
msgstr ""
"メモリ解放関数でひとつ重要なのは、処理待ちの例外にいっさい手をつけないことで"
"す。なぜなら、解放用の関数は Python インタプリタがスタックを元の状態に戻すと"
"きに呼ばれることが多いからです。そして (通常の関数からの復帰でなく) 例外のた"
"めにスタックが巻き戻されるときは、すでに発生している例外からメモリ解放関数を"
"守るものはありません。解放用の関数がおこなう動作が追加の Python のコードを実"
"行してしまうと、それらは例外が発生していることを検知するかもしれません。これ"
"はインタプリタが誤解させるエラーを発生させることにつながります。これを防ぐ正"
"しい方法は、安全でない操作を実行する前に処理待ちの例外を保存しておき、終わっ"
"たらそれを元に戻すことです。これは :c:func:`PyErr_Fetch` およ"
"び :c:func:`PyErr_Restore` 関数を使うことによって可能になります::"
msgid ""
"static void\n"
"my_dealloc(PyObject *obj)\n"
"{\n"
" MyObject *self = (MyObject *) obj;\n"
" PyObject *cbresult;\n"
"\n"
" if (self->my_callback != NULL) {\n"
" PyObject *err_type, *err_value, *err_traceback;\n"
"\n"
" /* This saves the current exception state */\n"
" PyErr_Fetch(&err_type, &err_value, &err_traceback);\n"
"\n"
" cbresult = PyObject_CallNoArgs(self->my_callback);\n"
" if (cbresult == NULL) {\n"
" PyErr_WriteUnraisable(self->my_callback);\n"
" }\n"
" else {\n"
" Py_DECREF(cbresult);\n"
" }\n"
"\n"
" /* This restores the saved exception state */\n"
" PyErr_Restore(err_type, err_value, err_traceback);\n"
"\n"
" Py_DECREF(self->my_callback);\n"
" }\n"
" Py_TYPE(self)->tp_free(self);\n"
"}"
msgstr ""
"static void\n"
"my_dealloc(PyObject *obj)\n"
"{\n"
" MyObject *self = (MyObject *) obj;\n"
" PyObject *cbresult;\n"
"\n"
" if (self->my_callback != NULL) {\n"
" PyObject *err_type, *err_value, *err_traceback;\n"
"\n"
" /* 現在の例外の状態を保存する */\n"
" PyErr_Fetch(&err_type, &err_value, &err_traceback);\n"
"\n"
" cbresult = PyObject_CallNoArgs(self->my_callback);\n"
" if (cbresult == NULL) {\n"
" PyErr_WriteUnraisable(self->my_callback);\n"
" }\n"
" else {\n"
" Py_DECREF(cbresult);\n"
" }\n"
"\n"
" /* 保存した例外の状態を復元する */\n"
" PyErr_Restore(err_type, err_value, err_traceback);\n"
"\n"
" Py_DECREF(self->my_callback);\n"
" }\n"
" Py_TYPE(self)->tp_free(self);\n"
"}"
msgid ""
"There are limitations to what you can safely do in a deallocator function. "
"First, if your type supports garbage collection "
"(using :c:member:`~PyTypeObject.tp_traverse` and/"
"or :c:member:`~PyTypeObject.tp_clear`), some of the object's members can "
"have been cleared or finalized by the "
"time :c:member:`~PyTypeObject.tp_dealloc` is called. Second, "
"in :c:member:`~PyTypeObject.tp_dealloc`, your object is in an unstable "
"state: its reference count is equal to zero. Any call to a non-trivial "
"object or API (as in the example above) might end up "
"calling :c:member:`~PyTypeObject.tp_dealloc` again, causing a double free "
"and a crash."
msgstr ""
"メモリ解放関数で安全に行えることには制限があります。\n"
"まず、型が "
"(:c:member:`~PyTypeObject.tp_traverse`、:c:member:`~PyTypeObject.tp_clear` の"
"一方または両方を使って) ガベージコレクションをサポートする場"
"合、:c:member:`~PyTypeObject.tp_dealloc` が呼ばれる時点で、オブジェクトの一部"
"のメンバがすでにクリアされているか、ファイナライズされている可能性がありま"
"す。\n"
"また、:c:member:`~PyTypeObject.tp_dealloc` の中ではオブジェクトの参照カウント"
"がゼロになっており、不安定な状態にあります。\n"
"上の例のような単純でないオブジェクトや API の呼び出し"
"は、:c:member:`~PyTypeObject.tp_dealloc` を再び呼び出し、二重解放によるクラッ"
"シュを引き起こす可能性があります。"
#: ../../extending/newtypes.rst:147
msgid ""
"Starting with Python 3.4, it is recommended not to put any complex "
"finalization code in :c:member:`~PyTypeObject.tp_dealloc`, and instead use "
"the new :c:member:`~PyTypeObject.tp_finalize` type method."
msgstr ""
"Python 3.4 からは、複雑なファイナライズのコード"
"は :c:member:`~PyTypeObject.tp_dealloc` に置かず、代わりに新しく導入され"
"た :c:member:`~PyTypeObject.tp_finalize` という型メソッドを使うことが推奨され"
"ています。"
#: ../../extending/newtypes.rst:152
msgid ":pep:`442` explains the new finalization scheme."
msgstr ":pep:`442` で新しいファイナライズの仕組みが説明されています。"
#: ../../extending/newtypes.rst:159
msgid "Object Presentation"
msgstr "オブジェクト表現"
#: ../../extending/newtypes.rst:161
msgid ""
"In Python, there are two ways to generate a textual representation of an "
"object: the :func:`repr` function, and the :func:`str` function. "
"(The :func:`print` function just calls :func:`str`.) These handlers are "
"both optional."
msgstr ""
"Python では、オブジェクトの文字列表現を生成するのに 2つのやり方がありま"
"す: :func:`repr` 関数を使う方法と、 :func:`str` 関数を使う方法です。 "
"(:func:`print` 関数は単に :func:`str` を呼び出します。) これらのハンドラはど"
"ちらも省略できます。"
msgid ""
"reprfunc tp_repr;\n"
"reprfunc tp_str;"
msgstr ""
"reprfunc tp_repr;\n"
"reprfunc tp_str;"
#: ../../extending/newtypes.rst:170
msgid ""
"The :c:member:`~PyTypeObject.tp_repr` handler should return a string object "
"containing a representation of the instance for which it is called. Here is "
"a simple example::"
msgstr ""
":c:member:`~PyTypeObject.tp_repr` ハンドラは呼び出されたインスタンスの文字列"
"表現を格納した文字列オブジェクトを返す必要があります。簡単な例は以下のような"
"ものです::"
msgid ""
"static PyObject *\n"
"newdatatype_repr(PyObject *op)\n"
"{\n"
" newdatatypeobject *self = (newdatatypeobject *) op;\n"
" return PyUnicode_FromFormat(\"Repr-ified_newdatatype{{size:%d}}\",\n"
" self->obj_UnderlyingDatatypePtr->size);\n"
"}"
msgstr ""
"static PyObject *\n"
"newdatatype_repr(PyObject *op)\n"
"{\n"
" newdatatypeobject *self = (newdatatypeobject *) op;\n"
" return PyUnicode_FromFormat(\"Repr-ified_newdatatype{{size:%d}}\",\n"
" self->obj_UnderlyingDatatypePtr->size);\n"
"}"
msgid ""
"If no :c:member:`~PyTypeObject.tp_repr` handler is specified, the "
"interpreter will supply a representation that uses the "
"type's :c:member:`~PyTypeObject.tp_name` and a uniquely identifying value "
"for the object."
msgstr ""
":c:member:`~PyTypeObject.tp_repr` ハンドラを指定しない場合、インタープリタは"
"その型の :c:member:`~PyTypeObject.tp_name` とオブジェクトを一意に識別する値を"
"使った表現を生成します。"
#: ../../extending/newtypes.rst:186
msgid ""
"The :c:member:`~PyTypeObject.tp_str` handler is to :func:`str` what "
"the :c:member:`~PyTypeObject.tp_repr` handler described above is "
"to :func:`repr`; that is, it is called when Python code calls :func:`str` on "
"an instance of your object. Its implementation is very similar to "
"the :c:member:`~PyTypeObject.tp_repr` function, but the resulting string is "
"intended for human consumption. If :c:member:`~PyTypeObject.tp_str` is not "
"specified, the :c:member:`~PyTypeObject.tp_repr` handler is used instead."
msgstr ""
":c:member:`~PyTypeObject.tp_str` ハンドラと :func:`str` の関係は、上"
"の :c:member:`~PyTypeObject.tp_repr` ハンドラと :func:`repr` の関係に相当しま"
"す。つまり、これは Python のコードがオブジェクトのインスタンスに対し"
"て :func:`str` を呼び出したときに呼ばれます。この関数の実装"
"は :c:member:`~PyTypeObject.tp_repr` ハンドラのそれと非常に似ていますが、得ら"
"れる文字列表現は人間が読むことを意図されていま"
"す。 :c:member:`~PyTypeObject.tp_str` が指定されていない場合、かわり"
"に :c:member:`~PyTypeObject.tp_repr` ハンドラが使われます。"
#: ../../extending/newtypes.rst:193
msgid "Here is a simple example::"
msgstr "以下は簡単な例です::"
msgid ""
"static PyObject *\n"
"newdatatype_str(PyObject *op)\n"
"{\n"
" newdatatypeobject *self = (newdatatypeobject *) op;\n"
" return PyUnicode_FromFormat(\"Stringified_newdatatype{{size:%d}}\",\n"
" self->obj_UnderlyingDatatypePtr->size);\n"
"}"
msgstr ""
"static PyObject *\n"
"newdatatype_str(PyObject *op)\n"
"{\n"
" newdatatypeobject *self = (newdatatypeobject *) op;\n"
" return PyUnicode_FromFormat(\"Stringified_newdatatype{{size:%d}}\",\n"
" self->obj_UnderlyingDatatypePtr->size);\n"
"}"
#: ../../extending/newtypes.rst:206
msgid "Attribute Management"
msgstr "属性を管理する"
msgid ""
"For every object which can support attributes, the corresponding type must "
"provide the functions that control how the attributes are resolved. There "
"needs to be a function which can retrieve attributes (if any are defined), "
"and another to set attributes (if setting attributes is allowed). Removing "
"an attribute is a special case, for which the new value passed to the "
"handler is ``NULL``."
msgstr ""
"属性を持つオブジェクトでは、対応する型が属性の解決方法を制御する関数を提供す"
"る必要があります。\n"
"属性を定義する場合は取得用の関数が、属性の設定を許可する場合は設定用の関数が"
"必要です。\n"
"属性の削除は特別な場合で、ハンドラには新しい値として ``NULL`` を渡します。"
msgid ""
"Python supports two pairs of attribute handlers; a type that supports "
"attributes only needs to implement the functions for one pair. The "
"difference is that one pair takes the name of the attribute as "
"a :c:expr:`char\\*`, while the other accepts a :c:expr:`PyObject*`. Each "
"type can use whichever pair makes more sense for the implementation's "
"convenience. ::"
msgstr ""
"Python は属性ハンドラの組を二つサポートしています。\n"
"属性をサポートする型は、どちらか一組の関数だけを実装すれば十分です。\n"
"違いは、一方が属性名を :c:expr:`char\\*` で受け取り、もう一方"
"は :c:expr:`PyObject*` で受け取る点です。\n"
"各型は実装に都合のよい方を使えます。 ::"
msgid ""
"getattrfunc tp_getattr; /* char * version */\n"
"setattrfunc tp_setattr;\n"
"/* ... */\n"
"getattrofunc tp_getattro; /* PyObject * version */\n"
"setattrofunc tp_setattro;"
msgstr ""
"getattrfunc tp_getattr; /* char * 版 */\n"
"setattrfunc tp_setattr;\n"
"/* ... */\n"
"getattrofunc tp_getattro; /* PyObject * 版 */\n"
"setattrofunc tp_setattro;"
msgid ""
"If accessing attributes of an object is always a simple operation (this will "
"be explained shortly), there are generic implementations which can be used "
"to provide the :c:expr:`PyObject*` version of the attribute management "
"functions. The actual need for type-specific attribute handlers almost "
"completely disappeared starting with Python 2.2, though there are many "
"examples which have not been updated to use some of the new generic "
"mechanism that is available."
msgstr ""
"オブジェクトの属性へのアクセスが常に単純な操作で済む場合 (この後で説明しま"
"す)、:c:expr:`PyObject*` 版の属性管理関数として使える汎用の実装があります。\n"
"Python 2.2 以降、型固有の属性ハンドラが実際に必要になることはほとんどなくなり"
"ました。\n"
"ただし、新しい汎用の仕組みを使うように更新されていない例も数多くあります。"
#: ../../extending/newtypes.rst:237
msgid "Generic Attribute Management"
msgstr "総称的な属性を管理する"
#: ../../extending/newtypes.rst:239
msgid ""
"Most extension types only use *simple* attributes. So, what makes the "
"attributes simple? There are only a couple of conditions that must be met:"
msgstr ""
"ほとんどの型は *単純な* 属性を使うだけです。では、どのような属性が単純だとい"
"えるのでしょうか? それが満たすべき条件はごくわずかです:"
#: ../../extending/newtypes.rst:242
msgid ""
"The name of the attributes must be known when :c:func:`PyType_Ready` is "
"called."
msgstr ""
":c:func:`PyType_Ready` が呼ばれたとき、すでに属性の名前がわかっていること。"
msgid ""
"No special processing is needed to record that an attribute was looked up or "
"set, nor do actions need to be taken based on the value."
msgstr ""
"属性が取得または設定されたことを記録するための特別な処理も、属性の値に応じた"
"処理も不要であること。"
msgid ""
"Note that this list does not place any restrictions on the values of the "
"attributes, when the values are computed, or how relevant data is stored."
msgstr ""
"これらの条件は、属性の値、値を計算するタイミング、関連するデータの格納方法に"
"は何の制約も課しません。"
msgid ""
"When :c:func:`PyType_Ready` is called, it uses three tables referenced by "
"the type object to create :term:`descriptor`\\s which are placed in the "
"dictionary of the type object. Each descriptor controls access to one "
"attribute of the instance object. Each of the tables is optional; if all "
"three are ``NULL``, instances of the type will only have attributes that are "
"inherited from their base type, and should leave "
"the :c:member:`~PyTypeObject.tp_getattro` "
"and :c:member:`~PyTypeObject.tp_setattro` fields ``NULL`` as well, allowing "
"the base type to handle attributes."
msgstr ""
":c:func:`PyType_Ready` は、型オブジェクトが参照する三つのテーブルを使っ"
"て :term:`デスクリプタ <descriptor>` を作成し、型オブジェクトの辞書に格納しま"
"す。\n"
"各デスクリプタは、インスタンスオブジェクトの一つの属性へのアクセスを制御しま"
"す。\n"
"テーブルはいずれも省略可能です。\n"
"三つとも ``NULL`` の場合、その型のインスタンスが持つ属性は基底型から継承した"
"ものだけになります。\n"
"この場合、属性の処理を基底型に任せられるよう"
"に、:c:member:`~PyTypeObject.tp_getattro` "
"と :c:member:`~PyTypeObject.tp_setattro` フィールドも ``NULL`` にしてくださ"
"い。"
#: ../../extending/newtypes.rst:259
msgid "The tables are declared as three fields of the type object::"
msgstr "テーブルはタイプオブジェクト中の 3つのメンバとして宣言されています::"
msgid ""
"struct PyMethodDef *tp_methods;\n"
"struct PyMemberDef *tp_members;\n"
"struct PyGetSetDef *tp_getset;"
msgstr ""
"struct PyMethodDef *tp_methods;\n"
"struct PyMemberDef *tp_members;\n"
"struct PyGetSetDef *tp_getset;"
msgid ""
"If :c:member:`~PyTypeObject.tp_methods` is not ``NULL``, it must refer to an "
"array of :c:type:`PyMethodDef` structures. Each entry in the table is an "
"instance of this structure::"
msgstr ""
":c:member:`~PyTypeObject.tp_methods` が ``NULL`` でない場合"
"は、:c:type:`PyMethodDef` 構造体の配列を指す必要があります。\n"
"テーブル内の各エントリーは、次の構造体のインスタンスです。 ::"
msgid ""
"typedef struct PyMethodDef {\n"
" const char *ml_name; /* method name */\n"
" PyCFunction ml_meth; /* implementation function */\n"
" int ml_flags; /* flags */\n"
" const char *ml_doc; /* docstring */\n"
"} PyMethodDef;"
msgstr ""
"typedef struct PyMethodDef {\n"
" const char *ml_name; /* メソッド名 */\n"
" PyCFunction ml_meth; /* 実装関数 */\n"
" int ml_flags; /* フラグ */\n"
" const char *ml_doc; /* ドキュメント文字列 */\n"
"} PyMethodDef;"
msgid ""
"One entry should be defined for each method provided by the type; no entries "
"are needed for methods inherited from a base type. One additional entry is "
"needed at the end; it is a sentinel that marks the end of the array. "
"The :c:member:`~PyMethodDef.ml_name` field of the sentinel must be ``NULL``."
msgstr ""
"型が提供するメソッドごとに一つのエントリーを定義します。\n"
"基底型から継承するメソッドのエントリーは不要です。\n"
"末尾には、配列の終わりを示す番兵となるエントリーをもう一つ追加する必要があり"
"ます。\n"
"番兵の :c:member:`~PyMethodDef.ml_name` フィールドは ``NULL`` にしなければな"
"りません。"
#: ../../extending/newtypes.rst:281
msgid ""
"The second table is used to define attributes which map directly to data "
"stored in the instance. A variety of primitive C types are supported, and "
"access may be read-only or read-write. The structures in the table are "
"defined as::"
msgstr ""
"2番目のテーブルは、インスタンス中に格納されるデータと直接対応づけられた属性を"
"定義するのに使います。いくつもの C の原始的な型がサポートされており、アクセス"
"を読み出し専用にも読み書き可能にもできます。このテーブルで使われる構造体は次"
"のように定義されています::"
#: ../../extending/newtypes.rst:285
msgid ""
"typedef struct PyMemberDef {\n"
" const char *name;\n"
" int type;\n"
" int offset;\n"
" int flags;\n"
" const char *doc;\n"
"} PyMemberDef;"
msgstr ""
msgid ""
"For each entry in the table, a :term:`descriptor` will be constructed and "
"added to the type which will be able to extract a value from the instance "
"structure. The :c:member:`~PyMemberDef.type` field should contain a type "
"code like :c:macro:`Py_T_INT` or :c:macro:`Py_T_DOUBLE`; the value will be "
"used to determine how to convert Python values to and from C values. "
"The :c:member:`~PyMemberDef.flags` field is used to store flags which "
"control how the attribute can be accessed: you can set it "
"to :c:macro:`Py_READONLY` to prevent Python code from setting it."
msgstr ""
"テーブルの各エントリーから、インスタンス構造体の値を取り出せる :term:`デスク"
"リプタ <descriptor>` が作成され、型に追加されます。\n"
":c:member:`~PyMemberDef.type` フィールドには :c:macro:`Py_T_INT` "
"や :c:macro:`Py_T_DOUBLE` のような型コードを設定します。\n"
"この値は、Python の値と C の値を相互に変換する方法を決めるために使います。\n"
":c:member:`~PyMemberDef.flags` フィールドには、属性へのアクセス方法を制御する"
"フラグを格納します。\n"
":c:macro:`Py_READONLY` を設定すると、Python コードからの値の設定を禁止できま"
"す。"
msgid ""
"An interesting advantage of using the :c:member:`~PyTypeObject.tp_members` "
"table to build descriptors that are used at runtime is that any attribute "
"defined this way can have an associated doc string simply by providing the "
"text in the table. An application can use the introspection API to retrieve "
"the descriptor from the class object, and get the doc string using "
"its :attr:`~type.__doc__` attribute."
msgstr ""
":c:member:`~PyTypeObject.tp_members` テーブルから実行時に使うデスクリプタを作"
"成する方法には、興味深い利点があります。\n"
"この方法で定義した属性は、テーブルにテキストを指定するだけでドキュメント文字"
"列を関連付けられます。\n"
"アプリケーションはイントロスペクション API を使ってクラスオブジェクトからデス"
"クリプタを取得し、その :attr:`~type.__doc__` 属性からドキュメント文字列を取得"
"できます。"
#: ../../extending/newtypes.rst:307
msgid ""
"As with the :c:member:`~PyTypeObject.tp_methods` table, a sentinel entry "
"with a :c:member:`~PyMethodDef.ml_name` value of ``NULL`` is required."
msgstr ""
#: ../../extending/newtypes.rst:321
msgid "Type-specific Attribute Management"
msgstr "特定の型に特化した属性の管理"
msgid ""
"For simplicity, only the :c:expr:`char\\*` version will be demonstrated "
"here; the type of the name parameter is the only difference between "
"the :c:expr:`char\\*` and :c:expr:`PyObject*` flavors of the interface. This "
"example effectively does the same thing as the generic example above, but "
"does not use the generic support added in Python 2.2. It explains how the "
"handler functions are called, so that if you do need to extend their "
"functionality, you'll understand what needs to be done."
msgstr ""
"簡単にするため、ここでは :c:expr:`char\\*` 版だけを示します。\n"
"インターフェースの :c:expr:`char\\*` 版と :c:expr:`PyObject*` 版の違いは、名"
"前を渡す引数の型だけです。\n"
"この例は、上の汎用の例と実質的に同じ処理を行いますが、Python 2.2 で追加された"
"汎用の仕組みは使いません。\n"
"ハンドラ関数の呼び出し方を説明するので、機能を拡張する必要がある場合に、何を"
"すべきかが分かるでしょう。"
#: ../../extending/newtypes.rst:331
msgid ""
"The :c:member:`~PyTypeObject.tp_getattr` handler is called when the object "
"requires an attribute look-up. It is called in the same situations where "
"the :meth:`~object.__getattr__` method of a class would be called."
msgstr ""
#: ../../extending/newtypes.rst:335
msgid "Here is an example::"
msgstr "以下に例を示します。::"
msgid ""
"static PyObject *\n"
"newdatatype_getattr(PyObject *op, char *name)\n"
"{\n"
" newdatatypeobject *self = (newdatatypeobject *) op;\n"
" if (strcmp(name, \"data\") == 0) {\n"
" return PyLong_FromLong(self->data);\n"
" }\n"
"\n"
" PyErr_Format(PyExc_AttributeError,\n"
" \"'%.100s' object has no attribute '%.400s'\",\n"
" Py_TYPE(self)->tp_name, name);\n"
" return NULL;\n"
"}"
msgstr ""
"static PyObject *\n"
"newdatatype_getattr(PyObject *op, char *name)\n"
"{\n"
" newdatatypeobject *self = (newdatatypeobject *) op;\n"
" if (strcmp(name, \"data\") == 0) {\n"
" return PyLong_FromLong(self->data);\n"
" }\n"
"\n"
" PyErr_Format(PyExc_AttributeError,\n"
" \"'%.100s' object has no attribute '%.400s'\",\n"
" Py_TYPE(self)->tp_name, name);\n"
" return NULL;\n"
"}"
msgid ""
"The :c:member:`~PyTypeObject.tp_setattr` handler is called when "
"the :meth:`~object.__setattr__` or :meth:`~object.__delattr__` method of a "
"class instance would be called. When an attribute should be deleted, the "
"third parameter will be ``NULL``. Here is an example that simply raises an "
"exception; if this were really all you wanted, "
"the :c:member:`~PyTypeObject.tp_setattr` handler should be set to "
"``NULL``. ::"
msgstr ""
":c:member:`~PyTypeObject.tp_setattr` ハンドラは、クラスのインスタンス"
"の :meth:`~object.__setattr__` または :meth:`~object.__delattr__` メソッドが"
"呼ばれる状況で呼び出されます。\n"
"属性を削除する場合、第 3 引数は ``NULL`` になります。\n"
"次は単に例外を送出する例です。\n"
"本当にこれだけを行いたいのであれば、:c:member:`~PyTypeObject.tp_setattr` ハン"
"ドラを ``NULL`` に設定してください。 ::"
msgid ""
"static int\n"
"newdatatype_setattr(PyObject *op, char *name, PyObject *v)\n"
"{\n"
" PyErr_Format(PyExc_RuntimeError, \"Read-only attribute: %s\", name);\n"
" return -1;\n"
"}"
msgstr ""
"static int\n"
"newdatatype_setattr(PyObject *op, char *name, PyObject *v)\n"
"{\n"
" PyErr_Format(PyExc_RuntimeError, \"Read-only attribute: %s\", name);\n"
" return -1;\n"
"}"
#: ../../extending/newtypes.rst:365
msgid "Object Comparison"
msgstr "オブジェクトの比較"
msgid "richcmpfunc tp_richcompare;"
msgstr "richcmpfunc tp_richcompare;"
msgid ""
"The :c:member:`~PyTypeObject.tp_richcompare` handler is called when "
"comparisons are needed. It is analogous to the :ref:`rich comparison "
"methods <richcmpfuncs>`, like :meth:`!__lt__`, and also called "
"by :c:func:`PyObject_RichCompare` and :c:func:`PyObject_RichCompareBool`."
msgstr ""
":c:member:`~PyTypeObject.tp_richcompare` ハンドラは、比較が必要なときに呼び出"
"されます。\n"
":meth:`!__lt__` などの :ref:`拡張比較メソッド <richcmpfuncs>` に相当"
"し、:c:func:`PyObject_RichCompare` と :c:func:`PyObject_RichCompareBool` から"
"も呼び出されます。"
msgid ""
"This function is called with two Python objects and the operator as "
"arguments, where the operator is one of ``Py_EQ``, ``Py_NE``, ``Py_LE``, "
"``Py_GE``, ``Py_LT`` or ``Py_GT``. It should compare the two objects with "
"respect to the specified operator and return ``Py_True`` or ``Py_False`` if "
"the comparison is successful, ``Py_NotImplemented`` to indicate that "
"comparison is not implemented and the other object's comparison method "
"should be tried, or ``NULL`` if an exception was set."
msgstr ""
"この関数は、二つの Python オブジェクトと演算子を引数として受け取ります。\n"
"演算子は ``Py_EQ``、``Py_NE``、``Py_LE``、``Py_GE``、``Py_LT``、``Py_GT`` の"
"いずれかです。\n"
"指定された演算子で二つのオブジェクトを比較し、比較が成功した場合は "
"``Py_True`` または ``Py_False`` を返してください。\n"
"比較が実装されておらず、もう一方のオブジェクトの比較メソッドを試すべきことを"
"示すには ``Py_NotImplemented`` を、例外を設定した場合は ``NULL`` を返してくだ"
"さい。"
#: ../../extending/newtypes.rst:384
msgid ""
"Here is a sample implementation, for a datatype that is considered equal if "
"the size of an internal pointer is equal::"
msgstr ""
"これは内部ポインタのサイズが等しければ等しいと見なすデータ型のサンプル実装で"
"す::"
msgid ""
"static PyObject *\n"
"newdatatype_richcmp(PyObject *lhs, PyObject *rhs, int op)\n"
"{\n"
" newdatatypeobject *obj1 = (newdatatypeobject *) lhs;\n"
" newdatatypeobject *obj2 = (newdatatypeobject *) rhs;\n"
" PyObject *result;\n"
" int c, size1, size2;\n"
"\n"
" /* code to make sure that both arguments are of type\n"
" newdatatype omitted */\n"
"\n"
" size1 = obj1->obj_UnderlyingDatatypePtr->size;\n"
" size2 = obj2->obj_UnderlyingDatatypePtr->size;\n"
"\n"
" switch (op) {\n"
" case Py_LT: c = size1 < size2; break;\n"
" case Py_LE: c = size1 <= size2; break;\n"
" case Py_EQ: c = size1 == size2; break;\n"
" case Py_NE: c = size1 != size2; break;\n"
" case Py_GT: c = size1 > size2; break;\n"
" case Py_GE: c = size1 >= size2; break;\n"
" }\n"
" result = c ? Py_True : Py_False;\n"
" return Py_NewRef(result);\n"
" }"
msgstr ""
"static PyObject *\n"
View remainder of file in raw view
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.