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
|
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE chapter SYSTEM "chapter.dtd">
<chapter>
<header>
<copyright>
<year>2002</year><year>2021</year>
<holder>Ericsson AB. All Rights Reserved.</holder>
</copyright>
<legalnotice>
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
</legalnotice>
<title>TFTP Release Notes</title>
<prepared></prepared>
<responsible></responsible>
<docno></docno>
<approved></approved>
<checked></checked>
<date>2018-03-22</date>
<rev>A</rev>
<file>notes.xml</file>
</header>
<section><title>Tftp 1.0.4</title>
<section><title>Improvements and New Features</title>
<list>
<item>
<p>
Replace size/1 with either tuple_size/1 or byte_size/1</p>
<p>
The <c>size/1</c> BIF is not optimized by the JIT, and
its use can result in worse types for Dialyzer.</p>
<p>
When one knows that the value being tested must be a
tuple, <c>tuple_size/1</c> should always be preferred.</p>
<p>
When one knows that the value being tested must be a
binary, <c>byte_size/1</c> should be preferred. However,
<c>byte_size/1</c> also accepts a bitstring (rounding up
size to a whole number of bytes), so one must make sure
that the call to <c>byte_size/</c> is preceded by a call
to <c>is_binary/1</c> to ensure that bitstrings are
rejected. Note that the compiler removes redundant calls
to <c>is_binary/1</c>, so if one is not sure whether
previous code had made sure that the argument is a
binary, it does not harm to add an <c>is_binary/1</c>
test immediately before the call to <c>byte_size/1</c>.</p>
<p>
Own Id: OTP-18432 Aux Id:
GH-6672,PR-6793,PR-6784,PR-6787,PR-6785,PR-6682,PR-6800,PR-6797,PR-6798,PR-6799,PR-6796,PR-6813,PR-6671,PR-6673,PR-6684,PR-6694,GH-6677,PR-6696,PR-6670,PR-6674 </p>
</item>
</list>
</section>
</section>
<section><title>Tftp 1.0.3</title>
<section><title>Fixed Bugs and Malfunctions</title>
<list>
<item>
<p>Missing runtime dependencies has been added to this
application.</p>
<p>
Own Id: OTP-17243 Aux Id: PR-4557 </p>
</item>
</list>
</section>
</section>
<section><title>Tftp 1.0.2</title>
<section><title>Improvements and New Features</title>
<list>
<item>
<p>
Removed compiler warnings.</p>
<p>
Own Id: OTP-16317 Aux Id: OTP-16183 </p>
</item>
</list>
</section>
</section>
<section><title>Tftp 1.0.1</title>
<section><title>Fixed Bugs and Malfunctions</title>
<list>
<item>
<p>
Improved documentation.</p>
<p>
Own Id: OTP-15190</p>
</item>
</list>
</section>
</section>
<section><title>TFTP 1.0</title>
<section><title>First released version</title>
<list>
<item>
<p>
Inets application was split into multiple smaller protocol specific applications.
The TFTP application is a standalone TFTP client and server with the same functionality as
TFTP in Inets.</p>
<p>
Own Id: OTP-14113</p>
</item>
</list>
</section>
</section>
</chapter>
|
