Skip to content

Correct indentation on file reference/datetime/datetimeinterface.xml #4454

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Apr 24, 2025
Merged

Correct indentation on file reference/datetime/datetimeinterface.xml #4454

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
2e7b3ae
Correct indentation
Marqitos Feb 9, 2025
237ab4f
#4453 - Correct indentation on file `reference/datetime/datetime.xml`
Marqitos Feb 9, 2025
be66a6f
#4453 - Correct indentation on file `reference/datetime/functions/str…
Marqitos Feb 10, 2025
96e9ded
#4453 - Correct indentation on file `reference/datetime/functions/str…
Marqitos Feb 10, 2025
b33a463
Correct indentation on `/reference\uopz/**`
Marqitos Mar 11, 2025
fabf061
Trimming white-spaces
Marqitos Mar 11, 2025
666524c
Correct indentation on `/reference/sync/**`
Marqitos Mar 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion reference/bc/functions/bcpow.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,7 @@ echo bcpow('5', '2', 2); // prints "25", not "25.00"
<simplelist>
<member><function>bcpowmod</function></member>
<member><function>bcsqrt</function></member>
<member><methodname>BcMath\Number::pow</methodname></member>
<member><methodname>BcMath\Number::pow</methodname></member>
</simplelist>
</para>
</refsect1>
Expand Down
78 changes: 39 additions & 39 deletions reference/datetime/datetime.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,45 +64,45 @@
<!-- }}} -->

</section>
<section role="changelog" xml:id="datetime.changelog"><!-- {{{ -->
&reftitle.changelog;
<para>
<informaltable>
<tgroup cols="2">
<thead>
<row>
<entry>&Version;</entry>
<entry>&Description;</entry>
</row>
</thead>
<tbody>
<row>
<entry>8.4.0</entry>
<entry>
The class constants are now typed.
</entry>
</row>
<row>
<entry>7.2.0</entry>
<entry>
The class constants of <classname>DateTime</classname> are now defined
on <classname>DateTimeInterface</classname>.
</entry>
</row>
<row>
<entry>7.1.0</entry>
<entry>
The <classname>DateTime</classname> constructor now includes the
current microseconds in the constructed value. Before this, it would
always initialise the microseconds to <literal>0</literal>.
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
</section><!-- }}} -->

<section role="changelog" xml:id="datetime.changelog"><!-- {{{ -->
&reftitle.changelog;
<para>
<informaltable>
<tgroup cols="2">
<thead>
<row>
<entry>&Version;</entry>
<entry>&Description;</entry>
</row>
</thead>
<tbody>
<row>
<entry>8.4.0</entry>
<entry>
The class constants are now typed.
</entry>
</row>
<row>
<entry>7.2.0</entry>
<entry>
The class constants of <classname>DateTime</classname> are now defined
on <classname>DateTimeInterface</classname>.
</entry>
</row>
<row>
<entry>7.1.0</entry>
<entry>
The <classname>DateTime</classname> constructor now includes the
current microseconds in the constructed value. Before this, it would
always initialise the microseconds to <literal>0</literal>.
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
</section><!-- }}} -->


</partintro>
Expand Down
70 changes: 35 additions & 35 deletions reference/datetime/datetimeinterface.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -353,41 +353,41 @@
</section>
<!-- }}} -->

<section role="changelog" xml:id="datetimeinterface.changelog"><!-- {{{ -->
&reftitle.changelog;
<para>
<informaltable>
<tgroup cols="2">
<thead>
<row>
<entry>&Version;</entry>
<entry>&Description;</entry>
</row>
</thead>
<tbody>
<row>
<entry>8.4.0</entry>
<entry>The class constants are now typed.</entry>
</row>
<row>
<entry>8.2.0</entry>
<entry>
The constant <constant linkend="datetimeinterface.constants.iso8601-expanded">DateTimeInterface::ISO8601_EXPANDED</constant>
was added.
</entry>
</row>
<row>
<entry>7.2.0</entry>
<entry>
The class constants of <classname>DateTime</classname> are now defined
on <interfacename>DateTimeInterface</interfacename>.
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
</section><!-- }}} -->
<section role="changelog" xml:id="datetimeinterface.changelog"><!-- {{{ -->
&reftitle.changelog;
<para>
<informaltable>
<tgroup cols="2">
<thead>
<row>
<entry>&Version;</entry>
<entry>&Description;</entry>
</row>
</thead>
<tbody>
<row>
<entry>8.4.0</entry>
<entry>The class constants are now typed.</entry>
</row>
<row>
<entry>8.2.0</entry>
<entry>
The constant <constant linkend="datetimeinterface.constants.iso8601-expanded">DateTimeInterface::ISO8601_EXPANDED</constant>
was added.
</entry>
</row>
<row>
<entry>7.2.0</entry>
<entry>
The class constants of <classname>DateTime</classname> are now defined
on <interfacename>DateTimeInterface</interfacename>.
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
</section><!-- }}} -->

</partintro>

Expand Down
88 changes: 44 additions & 44 deletions reference/datetime/functions/strptime.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,9 +150,9 @@
</para>
</refsect1>

<refsect1 role="examples">
&reftitle.examples;
<para>
<refsect1 role="examples">
&reftitle.examples;
<para>
<example>
<title><function>strptime</function> example</title>
<programlisting role="php">
Expand All @@ -166,9 +166,9 @@ echo "$strf\n";
print_r(strptime($strf, $format));
?>
]]>
</programlisting>
&example.outputs.similar;
<screen>
</programlisting>
&example.outputs.similar;
<screen>
<![CDATA[
03/10/2004 15:54:19

Expand All @@ -185,46 +185,46 @@ Array
[unparsed] =>
)
]]>
</screen>
</example>
</para>
</refsect1>
</screen>
</example>
</para>
</refsect1>

<refsect1 role="notes">
&reftitle.notes;
&note.no-windows;
<note>
<para>
Internally, this function calls the <literal>strptime()</literal>
function provided by the system's C library. This function can exhibit
noticeably different behaviour across different operating systems. The
use of <function>date_parse_from_format</function>, which does not
suffer from these issues, is recommended.
</para>
</note>
<note>
<para>
<literal>"tm_sec"</literal> includes any leap seconds (currently upto 2
a year). For more information on leap seconds, see the <link
xlink:href="&url.wiki.leap-seconds;">Wikipedia article
on leap seconds</link>.
</para>
</note>
</refsect1>
<refsect1 role="notes">
&reftitle.notes;
&note.no-windows;
<note>
<para>
Internally, this function calls the <literal>strptime()</literal>
function provided by the system's C library. This function can exhibit
noticeably different behaviour across different operating systems. The
use of <function>date_parse_from_format</function>, which does not
suffer from these issues, is recommended.
</para>
</note>
<note>
<para>
<literal>"tm_sec"</literal> includes any leap seconds (currently upto 2
a year). For more information on leap seconds, see the <link
xlink:href="&url.wiki.leap-seconds;">Wikipedia article
on leap seconds</link>.
</para>
</note>
</refsect1>

<refsect1 role="seealso">
&reftitle.seealso;
<para>
<simplelist>
<member><methodname>IntlDateFormatter::parse</methodname></member>
<member><methodname>DateTime::createFromFormat</methodname></member>
<member><function>checkdate</function></member>
<member><function>strftime</function></member>
<member><function>date_parse_from_format</function></member>
</simplelist>
</para>
</refsect1>
</refentry>
<refsect1 role="seealso">
&reftitle.seealso;
<para>
<simplelist>
<member><methodname>IntlDateFormatter::parse</methodname></member>
<member><methodname>DateTime::createFromFormat</methodname></member>
<member><function>checkdate</function></member>
<member><function>strftime</function></member>
<member><function>date_parse_from_format</function></member>
</simplelist>
</para>
</refsect1>
</refentry>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
Expand Down
32 changes: 16 additions & 16 deletions reference/sync/book.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,29 +9,29 @@
<preface xml:id="intro.sync">
&reftitle.intro;
<para>
The <literal>sync</literal> extension introduces cross-platform synchonization objects into PHP.
Named and unnamed Mutex, Semaphore, Event, Reader-Writer, and named Shared Memory
objects provide OS-level synchronization on both POSIX (e.g. Linux) and Windows
platforms.
The <literal>sync</literal> extension introduces cross-platform synchonization objects into PHP.
Named and unnamed Mutex, Semaphore, Event, Reader-Writer, and named Shared Memory
objects provide OS-level synchronization on both POSIX (e.g. Linux) and Windows
platforms.
</para>
<para>
Automatic cleanup of acquired synchronization objects takes place during extension
teardown. This means that if PHP prematurely terminates a script (e.g. script
execution time is exceeded), objects will not be left in an unknown state. The
only exception to this is if PHP itself crashes (e.g. an internal buffer overflow).
Automatic cleanup of acquired synchronization objects takes place during extension
teardown. This means that if PHP prematurely terminates a script (e.g. script
execution time is exceeded), objects will not be left in an unknown state. The
only exception to this is if PHP itself crashes (e.g. an internal buffer overflow).
</para>
<para>
Unnamed synchronization objects don't have a lot of use outside of a multithreaded
scenario. Unnamed objects are more useful in conjunction with the pthreads PECL
extension.
Unnamed synchronization objects don't have a lot of use outside of a multithreaded
scenario. Unnamed objects are more useful in conjunction with the pthreads PECL
extension.
</para>
<note>
<para>
Named objects require additional care to be used on all systems.
If an object is instantiated with a specific set of parameters, it must always
be instantiated with those parameters or the object will probably end up in an
inconsistent state until the next reboot or a system administrator cleans up
the mess.
Named objects require additional care to be used on all systems.
If an object is instantiated with a specific set of parameters, it must always
be instantiated with those parameters or the object will probably end up in an
inconsistent state until the next reboot or a system administrator cleans up
the mess.
</para>
</note>
</preface>
Expand Down
2 changes: 0 additions & 2 deletions reference/sync/configure.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,8 @@
<link xlink:href="&url.pecl.package;sync">&url.pecl.package;sync</link>
</para>


</section>


<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
Expand Down
2 changes: 1 addition & 1 deletion reference/sync/setup.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
<section xml:id="sync.requirements">
&reftitle.required;
<para>
A system with support for POSIX shared memory (shm_open()) or running Windows.
A system with support for POSIX shared memory (shm_open()) or running Windows.
</para>
</section>

Expand Down
13 changes: 7 additions & 6 deletions reference/sync/syncevent.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,14 +12,15 @@
<section xml:id="syncevent.intro">
&reftitle.intro;
<para>
A cross-platform, native implementation of named and unnamed event objects. Both automatic and manual event objects are supported.
A cross-platform, native implementation of named and unnamed event objects.
Both automatic and manual event objects are supported.
</para>
<para>
An event object waits, without polling, for the object to be fired/set.
One instance waits on the event object while another instance fires/sets
the event. Event objects are useful wherever a long-running process would
otherwise poll a resource (e.g. checking to see if uploaded data needs to
be processed).
An event object waits, without polling, for the object to be fired/set.
One instance waits on the event object while another instance fires/sets
the event. Event objects are useful wherever a long-running process would
otherwise poll a resource (e.g. checking to see if uploaded data needs to
be processed).
</para>
</section>
<!-- }}} -->
Expand Down
8 changes: 4 additions & 4 deletions reference/sync/syncmutex.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,12 +12,12 @@
<section xml:id="syncmutex.intro">
&reftitle.intro;
<para>
A cross-platform, native implementation of named and unnamed countable mutex objects.
A cross-platform, native implementation of named and unnamed countable mutex objects.
</para>
<para>
A mutex is a mutual exclusion object that restricts access to a shared resource (e.g. a file) to a single instance.
Countable mutexes acquire the mutex a single time and internally track the number of times the mutex is locked.
The mutex is unlocked as soon as it goes out of scope or is unlocked the same number of times that it was locked.
A mutex is a mutual exclusion object that restricts access to a shared resource (e.g. a file) to a single instance.
Countable mutexes acquire the mutex a single time and internally track the number of times the mutex is locked.
The mutex is unlocked as soon as it goes out of scope or is unlocked the same number of times that it was locked.
</para>
</section>
<!-- }}} -->
Expand Down
Loading