1
0
Fork 0
mirror of https://github.com/ganelson/inform.git synced 2024-06-17 07:40:47 +03:00

Minor documentation improvements

This commit is contained in:
Graham Nelson 2022-03-31 12:32:39 +01:00
parent ca2f51b347
commit e1be3d516d
9 changed files with 52 additions and 35 deletions

View file

@ -1,6 +1,6 @@
# Inform 7
v10.1.0-alpha.1+6U70 'Krypton' (28 March 2022)
v10.1.0-alpha.1+6U71 'Krypton' (31 March 2022)
## About Inform 7

View file

@ -1,3 +1,3 @@
Prerelease: alpha.1
Build Date: 28 March 2022
Build Number: 6U70
Build Date: 31 March 2022
Build Number: 6U71

View file

@ -138,7 +138,7 @@ project bundle with a pathname like <span class="extract"><span class="extract-s
through a little dance with <span class="extract"><span class="extract-syntax">Supervisor::optioneering_complete</span></span> to ensure that
if a project is already in the target list, Inbuild will use that; and if not,
but the user has specified a project to Inbuild already with <span class="extract"><span class="extract-syntax">-project</span></span> (a
command-line option recognised by <span class="extract"><span class="extract-syntax">inbuild</span></span> but not by us), then we add that
command-line option recognised by <span class="extract"><span class="extract-syntax">inform7</span></span> but not by us), then we add that
to the target list. Tne net result is that however the user indicates interest
in an Inform project bundle, it becomes both the Inbuild current project, and
also a member of our target list. It follows that we cannot have two project

View file

@ -280,11 +280,19 @@ case <span class="extract"><span class="extract-syntax">Acidity</span></span>, i
<span class="ConsoleText-element-syntax">$</span><span class="ConsoleText-plain-syntax"> </span><span class="ConsoleText-function-syntax">'inform7/Tangled/inform7'</span><span class="ConsoleText-identifier-syntax"> -source</span><span class="ConsoleText-plain-syntax"> inform7/Tests/Test\ Cases/Acidity.txt</span><span class="ConsoleText-identifier-syntax"> -o</span><span class="ConsoleText-plain-syntax"> Acidity.interb</span><span class="ConsoleText-identifier-syntax"> -format</span><span class="ConsoleText-plain-syntax">=binary</span>
<span class="ConsoleText-element-syntax">$</span><span class="ConsoleText-plain-syntax"> </span><span class="ConsoleText-function-syntax">'inform7/Tangled/inform7'</span><span class="ConsoleText-identifier-syntax"> -source</span><span class="ConsoleText-plain-syntax"> inform7/Tests/Test\ Cases/Acidity.txt</span><span class="ConsoleText-identifier-syntax"> -o</span><span class="ConsoleText-plain-syntax"> Acidity.intert</span><span class="ConsoleText-identifier-syntax"> -format</span><span class="ConsoleText-plain-syntax">=text</span>
</pre>
<p class="commentary">Be warned that they are large: they have several large kits linked into them
<p class="commentary">Be warned that these are large: they have several large kits linked into them
by the time they have reached this final state, and thus contain many modules.
<span class="extract"><span class="ConsoleText-extract-syntax">Acidity.intert</span></span> runs to about 250,000 lines of textual Inter.
</p>
<p class="commentary">It's also possible to access the Inter output by the top half of <a href="../inform7/index.html" class="internal">inform7</a>
before it passes through any linking process: simply add <span class="extract"><span class="ConsoleText-extract-syntax">-pipeline unlinked</span></span>.
Unlike the default pipeline <span class="extract"><span class="ConsoleText-extract-syntax">-pipeline compile</span></span>, <span class="extract"><span class="ConsoleText-extract-syntax">unlinked</span></span> just saves out
the Inter straight to an external file. (Of course, saving out unlinked Inter
to a format like Inform 6 will not produce viable code: linking is done for
a reason.)
</p>
<nav role="progress"><div class="progresscontainer">
<ul class="progressbar"><li class="progressprev"><a href="M-ia.html">&#10094;</a></li><li class="progresscurrentchapter">M</li><li class="progresssection"><a href="M-ui.html">ui</a></li><li class="progresssection"><a href="M-ti.html">ti</a></li><li class="progresssection"><a href="M-dpiti.html">dpiti</a></li><li class="progresssection"><a href="M-cpiti.html">cpiti</a></li><li class="progresssection"><a href="M-ip.html">ip</a></li><li class="progresssection"><a href="M-ia.html">ia</a></li><li class="progresscurrent">io</li><li class="progresssection"><a href="M-pas.html">pas</a></li><li class="progresssection"><a href="M-rc.html">rc</a></li><li class="progresschapter"><a href="1-mn.html">1</a></li><li class="progressnext"><a href="M-pas.html">&#10095;</a></li></ul></div>
</nav><!--End of weave-->

View file

@ -59,7 +59,7 @@ project bundle with a pathname like |Counterfeit Monkey.inform|. We go
through a little dance with |Supervisor::optioneering_complete| to ensure that
if a project is already in the target list, Inbuild will use that; and if not,
but the user has specified a project to Inbuild already with |-project| (a
command-line option recognised by |inbuild| but not by us), then we add that
command-line option recognised by |inform7| but not by us), then we add that
to the target list. Tne net result is that however the user indicates interest
in an Inform project bundle, it becomes both the Inbuild current project, and
also a member of our target list. It follows that we cannot have two project

View file

@ -1,10 +1,10 @@
Total memory consumption was 379106K = 370 MB
Total memory consumption was 379108K = 370 MB
66.6% was used for 2005891 objects, in 360763 frames in 316 x 800K = 252800K = 246 MB:
66.6% was used for 2006043 objects, in 360816 frames in 316 x 800K = 252800K = 246 MB:
10.7% inter_tree_node_array 58 x 8192 = 475136 objects, 41813824 bytes
6.2% text_stream_array 4341 x 100 = 434100 objects, 24448512 bytes
6.2% linked_list 43276 objects, 24234560 bytes
6.2% text_stream_array 4342 x 100 = 434200 objects, 24454144 bytes
6.2% linked_list 43296 objects, 24245760 bytes
3.6% inter_symbol_array 132 x 1024 = 135168 objects, 14061696 bytes
3.4% inter_error_stash_array 101 x 1024 = 103424 objects, 13241504 bytes
2.6% parse_node 129462 objects, 10356960 bytes
@ -115,24 +115,24 @@ Total memory consumption was 379106K = 370 MB
---- adjective_iname_holder 320 objects, 12800 bytes
---- uniqueness_count 454 objects, 10896 bytes
---- inter_construct 30 objects, 10320 bytes
---- filename 246 objects, 9840 bytes
---- filename 250 objects, 10000 bytes
---- stopwatch_timer 112 objects, 8960 bytes
---- build_vertex 64 objects, 7680 bytes
---- equation_node 68 objects, 7616 bytes
---- understanding_item_array 3 x 100 = 300 objects, 7296 bytes
---- shared_variable_array 1 x 100 objects, 7232 bytes
---- determiner 22 objects, 7216 bytes
---- build_vertex 60 objects, 7200 bytes
---- verb 108 objects, 6912 bytes
---- hierarchy_attachment_point 77 objects, 6776 bytes
---- inbuild_work 105 objects, 6720 bytes
---- text_literal_holder 163 objects, 6520 bytes
---- inbuild_work 101 objects, 6464 bytes
---- inbuild_copy 55 objects, 5720 bytes
---- inbuild_copy 59 objects, 6136 bytes
---- inbuild_edition 78 objects, 5616 bytes
---- heading_tree 20 objects, 5440 bytes
---- inbuild_edition 74 objects, 5328 bytes
---- explicit_action_array 1 x 100 objects, 4832 bytes
---- value_property_data 84 objects, 4704 bytes
---- parsing_pp_data 96 objects, 4608 bytes
---- compatibility_specification 86 objects, 4128 bytes
---- compatibility_specification 90 objects, 4320 bytes
---- command_line_switch 49 objects, 3920 bytes
---- activity 35 objects, 3920 bytes
---- submodule_request 94 objects, 3760 bytes
@ -152,11 +152,11 @@ Total memory consumption was 379106K = 370 MB
---- kind_constructor_casting_rule_array 1 x 100 objects, 2432 bytes
---- equation_symbol 30 objects, 2400 bytes
---- scene 1 object, 2096 bytes
---- build_script 60 objects, 1920 bytes
---- build_script 64 objects, 2048 bytes
---- inform_pipeline 28 objects, 1792 bytes
---- pronoun_usage 42 objects, 1680 bytes
---- table_contribution_array 1 x 100 objects, 1632 bytes
---- plugin 25 objects, 1600 bytes
---- inform_pipeline 24 objects, 1536 bytes
---- noun_filter_token 22 objects, 1408 bytes
---- inter_node_array 34 objects, 1360 bytes
---- special_meaning_holder 33 objects, 1320 bytes
@ -237,7 +237,7 @@ Total memory consumption was 379106K = 370 MB
33.3% was used for memory not allocated for objects:
19.7% text stream storage 76624528 bytes in 452128 claims
19.7% text stream storage 76626784 bytes in 452148 claims
1.1% dictionary storage 4544512 bytes in 6619 claims
---- sorting 744 bytes in 3 claims
1.8% source text 7200000 bytes in 3 claims
@ -255,5 +255,5 @@ Total memory consumption was 379106K = 370 MB
---- code generation workspace for objects 1336 bytes in 4 claims
---- emitter array storage 279776 bytes in 1995 claims
19.8% was overhead - 77062080 bytes = 75255K = 73 MB
19.8% was overhead - 77043072 bytes = 75237K = 73 MB

View file

@ -1,33 +1,33 @@
100.0% in inform7 run
68.6% in compilation to Inter
47.7% in //Sequence::undertake_queued_tasks//
4.7% in //MajorNodes::pre_pass//
68.2% in compilation to Inter
47.4% in //Sequence::undertake_queued_tasks//
4.5% in //MajorNodes::pre_pass//
3.4% in //MajorNodes::pass_1//
2.5% in //RTPhrasebook::compile_entries//
1.8% in //ImperativeDefinitions::assess_all//
1.4% in //RTKindConstructors::compile//
2.4% in //RTPhrasebook::compile_entries//
1.7% in //ImperativeDefinitions::assess_all//
1.5% in //RTKindConstructors::compile//
1.1% in //Sequence::lint_inter//
0.5% in //ImperativeDefinitions::compile_first_block//
0.5% in //MajorNodes::pass_2//
0.5% in //Sequence::undertake_queued_tasks//
0.5% in //Sequence::undertake_queued_tasks//
0.5% in //World::stage_V//
0.3% in //Sequence::undertake_queued_tasks//
0.1% in //CompletionModule::compile//
0.1% in //InferenceSubjects::emit_all//
0.1% in //RTKindConstructors::compile_permissions//
0.1% in //Task::make_built_in_kind_constructors//
0.1% in //World::stages_II_and_III//
2.0% not specifically accounted for
28.6% in running Inter pipeline
2.5% not specifically accounted for
28.9% in running Inter pipeline
10.2% in step 14/14: generate inform6 -> auto.inf
7.7% in step 5/14: load-binary-kits
6.4% in step 6/14: make-synoptic-module
1.4% in step 9/14: make-identifiers-unique
0.5% in step 4/14: compile-splats
1.5% in step 9/14: make-identifiers-unique
0.3% in step 12/14: eliminate-redundant-operations
0.3% in step 4/14: compile-splats
0.3% in step 7/14: shorten-wiring
0.3% in step 8/14: detect-indirect-calls
0.1% in step 11/14: eliminate-redundant-labels
0.9% not specifically accounted for
2.2% in supervisor
0.6% not specifically accounted for
1.4% not specifically accounted for
2.4% in supervisor
0.4% not specifically accounted for

View file

@ -0,0 +1,2 @@
read <- *in
generate -> *out

View file

@ -199,6 +199,13 @@ case |Acidity|, in binary and textual form:
$ 'inform7/Tangled/inform7' -source inform7/Tests/Test\ Cases/Acidity.txt -o Acidity.interb -format=binary
$ 'inform7/Tangled/inform7' -source inform7/Tests/Test\ Cases/Acidity.txt -o Acidity.intert -format=text
=
Be warned that they are large: they have several large kits linked into them
Be warned that these are large: they have several large kits linked into them
by the time they have reached this final state, and thus contain many modules.
|Acidity.intert| runs to about 250,000 lines of textual Inter.
It's also possible to access the Inter output by the top half of //inform7//
before it passes through any linking process: simply add |-pipeline unlinked|.
Unlike the default pipeline |-pipeline compile|, |unlinked| just saves out
the Inter straight to an external file. (Of course, saving out unlinked Inter
to a format like Inform 6 will not produce viable code: linking is done for
a reason.)