From 2e7b3aeaccf3c1079017bd17f19a7ebed99c081f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcos=20Porto=20Mari=C3=B1o?= Date: Sun, 9 Feb 2025 16:15:24 +0100 Subject: [PATCH 1/7] Correct indentation --- reference/datetime/datetimeinterface.xml | 70 ++++++++++++------------ 1 file changed, 35 insertions(+), 35 deletions(-) diff --git a/reference/datetime/datetimeinterface.xml b/reference/datetime/datetimeinterface.xml index 9c6529292fa5..54347e497552 100644 --- a/reference/datetime/datetimeinterface.xml +++ b/reference/datetime/datetimeinterface.xml @@ -353,41 +353,41 @@ -
- &reftitle.changelog; - - - - - - &Version; - &Description; - - - - - 8.4.0 - The class constants are now typed. - - - 8.2.0 - - The constant DateTimeInterface::ISO8601_EXPANDED - was added. - - - - 7.2.0 - - The class constants of DateTime are now defined - on DateTimeInterface. - - - - - - -
+
+ &reftitle.changelog; + + + + + + &Version; + &Description; + + + + + 8.4.0 + The class constants are now typed. + + + 8.2.0 + + The constant DateTimeInterface::ISO8601_EXPANDED + was added. + + + + 7.2.0 + + The class constants of DateTime are now defined + on DateTimeInterface. + + + + + + +
From 237ab4f2f1484e2d227b5bf8124250ea8c307eb6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcos=20Porto=20Mari=C3=B1o?= Date: Sun, 9 Feb 2025 21:19:16 +0100 Subject: [PATCH 2/7] #4453 - Correct indentation on file `reference/datetime/datetime.xml` --- reference/datetime/datetime.xml | 78 ++++++++++++++++----------------- 1 file changed, 39 insertions(+), 39 deletions(-) diff --git a/reference/datetime/datetime.xml b/reference/datetime/datetime.xml index 04227c08a472..dd915ac57f17 100644 --- a/reference/datetime/datetime.xml +++ b/reference/datetime/datetime.xml @@ -64,45 +64,45 @@ - -
- &reftitle.changelog; - - - - - - &Version; - &Description; - - - - - 8.4.0 - - The class constants are now typed. - - - - 7.2.0 - - The class constants of DateTime are now defined - on DateTimeInterface. - - - - 7.1.0 - - The DateTime constructor now includes the - current microseconds in the constructed value. Before this, it would - always initialise the microseconds to 0. - - - - - - -
+ +
+ &reftitle.changelog; + + + + + + &Version; + &Description; + + + + + 8.4.0 + + The class constants are now typed. + + + + 7.2.0 + + The class constants of DateTime are now defined + on DateTimeInterface. + + + + 7.1.0 + + The DateTime constructor now includes the + current microseconds in the constructed value. Before this, it would + always initialise the microseconds to 0. + + + + + + +
From be66a6f4de74c818763d56aa643e14e14583c10a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcos=20Porto=20Mari=C3=B1o?= Date: Mon, 10 Feb 2025 15:34:50 +0100 Subject: [PATCH 3/7] #4453 - Correct indentation on file `reference/datetime/functions/strptime.xml` --- reference/datetime/functions/strptime.xml | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/reference/datetime/functions/strptime.xml b/reference/datetime/functions/strptime.xml index 9adb25de600d..090d2731645c 100644 --- a/reference/datetime/functions/strptime.xml +++ b/reference/datetime/functions/strptime.xml @@ -150,9 +150,9 @@ - - &reftitle.examples; - + + &reftitle.examples; + <function>strptime</function> example @@ -166,9 +166,9 @@ echo "$strf\n"; print_r(strptime($strf, $format)); ?> ]]> - - &example.outputs.similar; - + + &example.outputs.similar; + ) ]]> - - - - + + + + &reftitle.notes; From 96e9ded5f74ebdd6f83a783bc8f60625c1968bea Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcos=20Porto=20Mari=C3=B1o?= Date: Mon, 10 Feb 2025 15:37:24 +0100 Subject: [PATCH 4/7] #4453 - Correct indentation on file `reference/datetime/functions/strptime.xml` --- reference/datetime/functions/strptime.xml | 68 +++++++++++------------ 1 file changed, 34 insertions(+), 34 deletions(-) diff --git a/reference/datetime/functions/strptime.xml b/reference/datetime/functions/strptime.xml index 090d2731645c..b4e3de531548 100644 --- a/reference/datetime/functions/strptime.xml +++ b/reference/datetime/functions/strptime.xml @@ -190,41 +190,41 @@ Array - - &reftitle.notes; - ¬e.no-windows; - - - Internally, this function calls the strptime() - function provided by the system's C library. This function can exhibit - noticeably different behaviour across different operating systems. The - use of date_parse_from_format, which does not - suffer from these issues, is recommended. - - - - - "tm_sec" includes any leap seconds (currently upto 2 - a year). For more information on leap seconds, see the Wikipedia article - on leap seconds. - - - + + &reftitle.notes; + ¬e.no-windows; + + + Internally, this function calls the strptime() + function provided by the system's C library. This function can exhibit + noticeably different behaviour across different operating systems. The + use of date_parse_from_format, which does not + suffer from these issues, is recommended. + + + + + "tm_sec" includes any leap seconds (currently upto 2 + a year). For more information on leap seconds, see the Wikipedia article + on leap seconds. + + + - - &reftitle.seealso; - - - IntlDateFormatter::parse - DateTime::createFromFormat - checkdate - strftime - date_parse_from_format - - - - + + &reftitle.seealso; + + + IntlDateFormatter::parse + DateTime::createFromFormat + checkdate + strftime + date_parse_from_format + + + + diff --git a/reference/sync/syncmutex.xml b/reference/sync/syncmutex.xml index 4de277019adb..2d8987642405 100644 --- a/reference/sync/syncmutex.xml +++ b/reference/sync/syncmutex.xml @@ -12,12 +12,12 @@
&reftitle.intro; - A cross-platform, native implementation of named and unnamed countable mutex objects. + A cross-platform, native implementation of named and unnamed countable mutex objects. - 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.
diff --git a/reference/sync/syncreaderwriter.xml b/reference/sync/syncreaderwriter.xml index f6f815fd60dc..e8f7cde824b8 100644 --- a/reference/sync/syncreaderwriter.xml +++ b/reference/sync/syncreaderwriter.xml @@ -12,12 +12,12 @@
&reftitle.intro; - A cross-platform, native implementation of named and unnamed reader-writer objects. + A cross-platform, native implementation of named and unnamed reader-writer objects. - A reader-writer object allows many readers or one writer to access a resource. - This is an efficient solution for managing resources where access will primarily be - read-only but exclusive write access is occasionally necessary. + A reader-writer object allows many readers or one writer to access a resource. + This is an efficient solution for managing resources where access will primarily be + read-only but exclusive write access is occasionally necessary.
diff --git a/reference/sync/syncsemaphore.xml b/reference/sync/syncsemaphore.xml index 92c0af8cc721..0e349353f651 100644 --- a/reference/sync/syncsemaphore.xml +++ b/reference/sync/syncsemaphore.xml @@ -12,12 +12,12 @@
&reftitle.intro; - A cross-platform, native implementation of named and unnamed semaphore objects. + A cross-platform, native implementation of named and unnamed semaphore objects. - A semaphore restricts access to a limited resource to a limited number of instances. - Semaphores differ from mutexes in that they can allow more than one instance to - access a resource at one time while a mutex only allows one instance at a time. + A semaphore restricts access to a limited resource to a limited number of instances. + Semaphores differ from mutexes in that they can allow more than one instance to + access a resource at one time while a mutex only allows one instance at a time.
diff --git a/reference/sync/syncsharedmemory.xml b/reference/sync/syncsharedmemory.xml index 3824c315c18d..2fc0cfaa1abc 100644 --- a/reference/sync/syncsharedmemory.xml +++ b/reference/sync/syncsharedmemory.xml @@ -12,17 +12,17 @@
&reftitle.intro; - A cross-platform, native, consistent implementation of named shared memory - objects. + A cross-platform, native, consistent implementation of named shared memory + objects. - Shared memory lets two separate processes communicate without the need for - complex pipes or sockets. There are several integer-based shared memory - implementations for PHP. Named shared memory is an alternative. + Shared memory lets two separate processes communicate without the need for + complex pipes or sockets. There are several integer-based shared memory + implementations for PHP. Named shared memory is an alternative. - Synchronization objects (e.g. SyncMutex) are still required to protect most - uses of shared memory. + Synchronization objects (e.g. SyncMutex) are still required to protect most + uses of shared memory.
diff --git a/reference/sync/syncsharedmemory/read.xml b/reference/sync/syncsharedmemory/read.xml index d8ca332b5b76..10b354b02694 100644 --- a/reference/sync/syncsharedmemory/read.xml +++ b/reference/sync/syncsharedmemory/read.xml @@ -15,7 +15,7 @@ intlength - Copies data from named shared memory. + Copies data from named shared memory. @@ -26,12 +26,12 @@ start - The start/offset, in bytes, to begin reading. + The start/offset, in bytes, to begin reading. - If the value is negative, the starting position will begin at the specified - number of bytes from the end of the shared memory segment. + If the value is negative, the starting position will begin at the specified + number of bytes from the end of the shared memory segment. @@ -40,15 +40,15 @@ length - The number of bytes to read. + The number of bytes to read. - If unspecified, reading will stop at the end of the shared memory segment. + If unspecified, reading will stop at the end of the shared memory segment. - If the value is negative, reading will stop the specified number of bytes - from the end of the shared memory segment. + If the value is negative, reading will stop the specified number of bytes + from the end of the shared memory segment. @@ -59,7 +59,7 @@ &reftitle.returnvalues; - A string containing the data read from shared memory. + A string containing the data read from shared memory.