Skip to content

Commit c9490d4

Browse files
MarqitosMarqitos
authored
[skip-revcheck] Correct indentation (#4454)
1 parent e908bfd commit c9490d4

34 files changed

+299
-286
lines changed

‎reference/bc/functions/bcpow.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -151,7 +151,7 @@ echo bcpow('5', '2', 2); // prints "25", not "25.00"
151151
<simplelist>
152152
<member><function>bcpowmod</function></member>
153153
<member><function>bcsqrt</function></member>
154-
<member><methodname>BcMath\Number::pow</methodname></member>
154+
<member><methodname>BcMath\Number::pow</methodname></member>
155155
</simplelist>
156156
</para>
157157
</refsect1>

‎reference/datetime/datetime.xml

+39-39
Original file line numberDiff line numberDiff line change
@@ -64,45 +64,45 @@
6464
<!-- }}} -->
6565

6666
</section>
67-
68-
<section role="changelog" xml:id="datetime.changelog"><!-- {{{ -->
69-
&reftitle.changelog;
70-
<para>
71-
<informaltable>
72-
<tgroup cols="2">
73-
<thead>
74-
<row>
75-
<entry>&Version;</entry>
76-
<entry>&Description;</entry>
77-
</row>
78-
</thead>
79-
<tbody>
80-
<row>
81-
<entry>8.4.0</entry>
82-
<entry>
83-
The class constants are now typed.
84-
</entry>
85-
</row>
86-
<row>
87-
<entry>7.2.0</entry>
88-
<entry>
89-
The class constants of <classname>DateTime</classname> are now defined
90-
on <classname>DateTimeInterface</classname>.
91-
</entry>
92-
</row>
93-
<row>
94-
<entry>7.1.0</entry>
95-
<entry>
96-
The <classname>DateTime</classname> constructor now includes the
97-
current microseconds in the constructed value. Before this, it would
98-
always initialise the microseconds to <literal>0</literal>.
99-
</entry>
100-
</row>
101-
</tbody>
102-
</tgroup>
103-
</informaltable>
104-
</para>
105-
</section><!-- }}} -->
67+
68+
<section role="changelog" xml:id="datetime.changelog"><!-- {{{ -->
69+
&reftitle.changelog;
70+
<para>
71+
<informaltable>
72+
<tgroup cols="2">
73+
<thead>
74+
<row>
75+
<entry>&Version;</entry>
76+
<entry>&Description;</entry>
77+
</row>
78+
</thead>
79+
<tbody>
80+
<row>
81+
<entry>8.4.0</entry>
82+
<entry>
83+
The class constants are now typed.
84+
</entry>
85+
</row>
86+
<row>
87+
<entry>7.2.0</entry>
88+
<entry>
89+
The class constants of <classname>DateTime</classname> are now defined
90+
on <classname>DateTimeInterface</classname>.
91+
</entry>
92+
</row>
93+
<row>
94+
<entry>7.1.0</entry>
95+
<entry>
96+
The <classname>DateTime</classname> constructor now includes the
97+
current microseconds in the constructed value. Before this, it would
98+
always initialise the microseconds to <literal>0</literal>.
99+
</entry>
100+
</row>
101+
</tbody>
102+
</tgroup>
103+
</informaltable>
104+
</para>
105+
</section><!-- }}} -->
106106

107107

108108
</partintro>

‎reference/datetime/datetimeinterface.xml

+35-35
Original file line numberDiff line numberDiff line change
@@ -353,41 +353,41 @@
353353
</section>
354354
<!-- }}} -->
355355

356-
<section role="changelog" xml:id="datetimeinterface.changelog"><!-- {{{ -->
357-
&reftitle.changelog;
358-
<para>
359-
<informaltable>
360-
<tgroup cols="2">
361-
<thead>
362-
<row>
363-
<entry>&Version;</entry>
364-
<entry>&Description;</entry>
365-
</row>
366-
</thead>
367-
<tbody>
368-
<row>
369-
<entry>8.4.0</entry>
370-
<entry>The class constants are now typed.</entry>
371-
</row>
372-
<row>
373-
<entry>8.2.0</entry>
374-
<entry>
375-
The constant <constant linkend="datetimeinterface.constants.iso8601-expanded">DateTimeInterface::ISO8601_EXPANDED</constant>
376-
was added.
377-
</entry>
378-
</row>
379-
<row>
380-
<entry>7.2.0</entry>
381-
<entry>
382-
The class constants of <classname>DateTime</classname> are now defined
383-
on <interfacename>DateTimeInterface</interfacename>.
384-
</entry>
385-
</row>
386-
</tbody>
387-
</tgroup>
388-
</informaltable>
389-
</para>
390-
</section><!-- }}} -->
356+
<section role="changelog" xml:id="datetimeinterface.changelog"><!-- {{{ -->
357+
&reftitle.changelog;
358+
<para>
359+
<informaltable>
360+
<tgroup cols="2">
361+
<thead>
362+
<row>
363+
<entry>&Version;</entry>
364+
<entry>&Description;</entry>
365+
</row>
366+
</thead>
367+
<tbody>
368+
<row>
369+
<entry>8.4.0</entry>
370+
<entry>The class constants are now typed.</entry>
371+
</row>
372+
<row>
373+
<entry>8.2.0</entry>
374+
<entry>
375+
The constant <constant linkend="datetimeinterface.constants.iso8601-expanded">DateTimeInterface::ISO8601_EXPANDED</constant>
376+
was added.
377+
</entry>
378+
</row>
379+
<row>
380+
<entry>7.2.0</entry>
381+
<entry>
382+
The class constants of <classname>DateTime</classname> are now defined
383+
on <interfacename>DateTimeInterface</interfacename>.
384+
</entry>
385+
</row>
386+
</tbody>
387+
</tgroup>
388+
</informaltable>
389+
</para>
390+
</section><!-- }}} -->
391391

392392
</partintro>
393393

‎reference/datetime/functions/strptime.xml

+44-44
Original file line numberDiff line numberDiff line change
@@ -150,9 +150,9 @@
150150
</para>
151151
</refsect1>
152152

153-
<refsect1 role="examples">
154-
&reftitle.examples;
155-
<para>
153+
<refsect1 role="examples">
154+
&reftitle.examples;
155+
<para>
156156
<example>
157157
<title><function>strptime</function> example</title>
158158
<programlisting role="php">
@@ -166,9 +166,9 @@ echo "$strf\n";
166166
print_r(strptime($strf, $format));
167167
?>
168168
]]>
169-
</programlisting>
170-
&example.outputs.similar;
171-
<screen>
169+
</programlisting>
170+
&example.outputs.similar;
171+
<screen>
172172
<![CDATA[
173173
03/10/2004 15:54:19
174174
@@ -185,46 +185,46 @@ Array
185185
[unparsed] =>
186186
)
187187
]]>
188-
</screen>
189-
</example>
190-
</para>
191-
</refsect1>
188+
</screen>
189+
</example>
190+
</para>
191+
</refsect1>
192192

193-
<refsect1 role="notes">
194-
&reftitle.notes;
195-
&note.no-windows;
196-
<note>
197-
<para>
198-
Internally, this function calls the <literal>strptime()</literal>
199-
function provided by the system's C library. This function can exhibit
200-
noticeably different behaviour across different operating systems. The
201-
use of <function>date_parse_from_format</function>, which does not
202-
suffer from these issues, is recommended.
203-
</para>
204-
</note>
205-
<note>
206-
<para>
207-
<literal>"tm_sec"</literal> includes any leap seconds (currently upto 2
208-
a year). For more information on leap seconds, see the <link
209-
xlink:href="&url.wiki.leap-seconds;">Wikipedia article
210-
on leap seconds</link>.
211-
</para>
212-
</note>
213-
</refsect1>
193+
<refsect1 role="notes">
194+
&reftitle.notes;
195+
&note.no-windows;
196+
<note>
197+
<para>
198+
Internally, this function calls the <literal>strptime()</literal>
199+
function provided by the system's C library. This function can exhibit
200+
noticeably different behaviour across different operating systems. The
201+
use of <function>date_parse_from_format</function>, which does not
202+
suffer from these issues, is recommended.
203+
</para>
204+
</note>
205+
<note>
206+
<para>
207+
<literal>"tm_sec"</literal> includes any leap seconds (currently upto 2
208+
a year). For more information on leap seconds, see the <link
209+
xlink:href="&url.wiki.leap-seconds;">Wikipedia article
210+
on leap seconds</link>.
211+
</para>
212+
</note>
213+
</refsect1>
214214

215-
<refsect1 role="seealso">
216-
&reftitle.seealso;
217-
<para>
218-
<simplelist>
219-
<member><methodname>IntlDateFormatter::parse</methodname></member>
220-
<member><methodname>DateTime::createFromFormat</methodname></member>
221-
<member><function>checkdate</function></member>
222-
<member><function>strftime</function></member>
223-
<member><function>date_parse_from_format</function></member>
224-
</simplelist>
225-
</para>
226-
</refsect1>
227-
</refentry>
215+
<refsect1 role="seealso">
216+
&reftitle.seealso;
217+
<para>
218+
<simplelist>
219+
<member><methodname>IntlDateFormatter::parse</methodname></member>
220+
<member><methodname>DateTime::createFromFormat</methodname></member>
221+
<member><function>checkdate</function></member>
222+
<member><function>strftime</function></member>
223+
<member><function>date_parse_from_format</function></member>
224+
</simplelist>
225+
</para>
226+
</refsect1>
227+
</refentry>
228228
<!-- Keep this comment at the end of the file
229229
Local variables:
230230
mode: sgml

‎reference/sync/book.xml

+16-16
Original file line numberDiff line numberDiff line change
@@ -9,29 +9,29 @@
99
<preface xml:id="intro.sync">
1010
&reftitle.intro;
1111
<para>
12-
The <literal>sync</literal> extension introduces cross-platform synchonization objects into PHP.
13-
Named and unnamed Mutex, Semaphore, Event, Reader-Writer, and named Shared Memory
14-
objects provide OS-level synchronization on both POSIX (e.g. Linux) and Windows
15-
platforms.
12+
The <literal>sync</literal> extension introduces cross-platform synchonization objects into PHP.
13+
Named and unnamed Mutex, Semaphore, Event, Reader-Writer, and named Shared Memory
14+
objects provide OS-level synchronization on both POSIX (e.g. Linux) and Windows
15+
platforms.
1616
</para>
1717
<para>
18-
Automatic cleanup of acquired synchronization objects takes place during extension
19-
teardown. This means that if PHP prematurely terminates a script (e.g. script
20-
execution time is exceeded), objects will not be left in an unknown state. The
21-
only exception to this is if PHP itself crashes (e.g. an internal buffer overflow).
18+
Automatic cleanup of acquired synchronization objects takes place during extension
19+
teardown. This means that if PHP prematurely terminates a script (e.g. script
20+
execution time is exceeded), objects will not be left in an unknown state. The
21+
only exception to this is if PHP itself crashes (e.g. an internal buffer overflow).
2222
</para>
2323
<para>
24-
Unnamed synchronization objects don't have a lot of use outside of a multithreaded
25-
scenario. Unnamed objects are more useful in conjunction with the pthreads PECL
26-
extension.
24+
Unnamed synchronization objects don't have a lot of use outside of a multithreaded
25+
scenario. Unnamed objects are more useful in conjunction with the pthreads PECL
26+
extension.
2727
</para>
2828
<note>
2929
<para>
30-
Named objects require additional care to be used on all systems.
31-
If an object is instantiated with a specific set of parameters, it must always
32-
be instantiated with those parameters or the object will probably end up in an
33-
inconsistent state until the next reboot or a system administrator cleans up
34-
the mess.
30+
Named objects require additional care to be used on all systems.
31+
If an object is instantiated with a specific set of parameters, it must always
32+
be instantiated with those parameters or the object will probably end up in an
33+
inconsistent state until the next reboot or a system administrator cleans up
34+
the mess.
3535
</para>
3636
</note>
3737
</preface>

‎reference/sync/configure.xml

-2
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,8 @@
99
<link xlink:href="&url.pecl.package;sync">&url.pecl.package;sync</link>
1010
</para>
1111

12-
1312
</section>
1413

15-
1614
<!-- Keep this comment at the end of the file
1715
Local variables:
1816
mode: sgml

‎reference/sync/setup.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
<section xml:id="sync.requirements">
88
&reftitle.required;
99
<para>
10-
A system with support for POSIX shared memory (shm_open()) or running Windows.
10+
A system with support for POSIX shared memory (shm_open()) or running Windows.
1111
</para>
1212
</section>
1313

‎reference/sync/syncevent.xml

+7-6
Original file line numberDiff line numberDiff line change
@@ -12,14 +12,15 @@
1212
<section xml:id="syncevent.intro">
1313
&reftitle.intro;
1414
<para>
15-
A cross-platform, native implementation of named and unnamed event objects. Both automatic and manual event objects are supported.
15+
A cross-platform, native implementation of named and unnamed event objects.
16+
Both automatic and manual event objects are supported.
1617
</para>
1718
<para>
18-
An event object waits, without polling, for the object to be fired/set.
19-
One instance waits on the event object while another instance fires/sets
20-
the event. Event objects are useful wherever a long-running process would
21-
otherwise poll a resource (e.g. checking to see if uploaded data needs to
22-
be processed).
19+
An event object waits, without polling, for the object to be fired/set.
20+
One instance waits on the event object while another instance fires/sets
21+
the event. Event objects are useful wherever a long-running process would
22+
otherwise poll a resource (e.g. checking to see if uploaded data needs to
23+
be processed).
2324
</para>
2425
</section>
2526
<!-- }}} -->

‎reference/sync/syncmutex.xml

+4-4
Original file line numberDiff line numberDiff line change
@@ -12,12 +12,12 @@
1212
<section xml:id="syncmutex.intro">
1313
&reftitle.intro;
1414
<para>
15-
A cross-platform, native implementation of named and unnamed countable mutex objects.
15+
A cross-platform, native implementation of named and unnamed countable mutex objects.
1616
</para>
1717
<para>
18-
A mutex is a mutual exclusion object that restricts access to a shared resource (e.g. a file) to a single instance.
19-
Countable mutexes acquire the mutex a single time and internally track the number of times the mutex is locked.
20-
The mutex is unlocked as soon as it goes out of scope or is unlocked the same number of times that it was locked.
18+
A mutex is a mutual exclusion object that restricts access to a shared resource (e.g. a file) to a single instance.
19+
Countable mutexes acquire the mutex a single time and internally track the number of times the mutex is locked.
20+
The mutex is unlocked as soon as it goes out of scope or is unlocked the same number of times that it was locked.
2121
</para>
2222
</section>
2323
<!-- }}} -->

0 commit comments

Comments
 (0)