From 953b858de46f46f42e2ba45ba30a9b0b278a526d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= Date: Mon, 17 Dec 2012 16:25:59 +0100 Subject: Remove the 'inline' and '{inline,OutputFile}' options --- lib/asn1/doc/src/asn1_ug.xml | 43 ++----------------------------------------- lib/asn1/doc/src/asn1ct.xml | 24 +----------------------- 2 files changed, 3 insertions(+), 64 deletions(-) (limited to 'lib/asn1/doc') diff --git a/lib/asn1/doc/src/asn1_ug.xml b/lib/asn1/doc/src/asn1_ug.xml index 6cb251c3e2..ecca287670 100644 --- a/lib/asn1/doc/src/asn1_ug.xml +++ b/lib/asn1/doc/src/asn1_ug.xml @@ -352,22 +352,6 @@ erlc -o ../asnfiles -I ../asnfiles -I /usr/local/standards/asn1 Person.asn list or a binary. Earlier versions of the compiler ignored those following bytes.

- {inline,OutputName} - -

Compiling with this option gives one output module - containing all asn1 run-time functionality. The asn1 specs - are provided in a target module Module.set.asn as - described in the reference manual. The name of the resulting module - containing generated encode/decode functions and inlined - run-time functions will be OutputName.erl. The - merging/inlining of code is done by the igor module - of syntax_tools. By default the functions generated - from the first asn1 spec in the .set.asn are - exported, unless a {export,[atom()]} or - {export_all,true} option are provided. The list of - atoms are names of choosen asn1 specs from the - .set.asn file. See further examples of usage below

- +'Any Erlc Option'

You may add any option to the Erlang compiler when @@ -454,21 +438,8 @@ asn1rt:decode('H323-MESSAGES','SomeChoiceType',Bytes). any reason. Maybe you need to compile the same specs for different encoding/decoding standards. You want only one resulting module. - If it is crucial to have a minimal system. Using - {inline,OutputModule} includes all necessary run-time - functions of the asn1 application, but skips those modules not - used. - Upgrading issues: Even if you upgrade your Erlang system - you may want to continue running the old asn1 run-time - functionality. - Performance issues: If you have an asn1 system with a lot - of cross references you may gain in performance. Measurements - must be done for each case. -

You may choose either the plain multi file compilation that just - merges the chosen asn1 specs or the {inline,OutputModule} - that also includes the used asn1 run-time functionality.

-

For both cases you need to specify which asn1 specs you will +

You need to specify which asn1 specs you will compile in a module that must have the extension .set.asn. You chose name of the module and provide the names of the asn1 specs. For instance, if you have the specs @@ -482,17 +453,7 @@ File3.asn ~> erlc MyModule.set.asn

the result will be one merged module MyModule.erl with - the generated code from the three asn1 specs. But if you compile - with:

- -~> erlc +"{inline,'OutputModule'}" MyModule.set.asn -

the result will be a module OutputModule.erl that - contains all encode/decode functions for the three asn1 specs and - all used functions from the asn1 run-time modules, in this case - asn1rt_ber_bin. In the former case all encode/decode - functions are exported but in the latter only the encode/decode - functions of the first spec in the .set.asn, i.e. those - from File1.asn. + the generated code from the three asn1 specs.

diff --git a/lib/asn1/doc/src/asn1ct.xml b/lib/asn1/doc/src/asn1ct.xml index bb3c6a4f0f..7ad4d14610 100644 --- a/lib/asn1/doc/src/asn1ct.xml +++ b/lib/asn1/doc/src/asn1ct.xml @@ -65,7 +65,7 @@ Options = [Option| OldOption] Option = ber | per | uper | der | compact_bit_string | noobj | {n2n, EnumTypeName} |{outdir, Dir} | {i, IncludeDir} | - asn1config | undec_rest | {inline, OutputName} | inline | + asn1config | undec_rest | {macro_name_prefix, Prefix} | {record_name_prefix, Prefix} | verbose | warnings_as_errors OldOption = ber | per Reason = term() @@ -233,28 +233,6 @@ Binary = binary() list or a binary. Earlier versions of the compiler ignored those following bytes.

 - {inline, OutputName} - -

Compiling with this option gives one output module - containing all asn1 run-time functionality. The asn1 specs - are provided in a target module Module.set.asn as described - above. The name of the - resulting module containing generated encode/decode functions - and in-lined run-time functions will be - OutputName.erl. The merging/in-lining of code is done - by the igor module of syntax_tools. By default - the functions generated from the first asn1 spec in the - .set.asn are exported, unless a - {export, [atom()]} or {export_all, true} option - are provided. The list of atoms are names of chosen asn1 - specs from the .set.asn file.

- - inline - -

It is also possible to use the sole argument inline. - It is as {inline, OutputName}, but the output file gets the - default name of the source .set.asn file.

- {macro_name_prefix, Prefix}

All macro names generated by the compiler are prefixed with -- cgit v1.2.3