info > Date::Manip::Interfaces

Che Dong

Not found locally for Date::Manip::Interfaces. Try Google search

The user wants me to transform this man page HTML into an emoji-rich version. Let me analyze the content carefully: This is a Perl module documentation for `Date::Manip::Interfaces`. It's a descriptive document, not a command reference. There are no actual command-line options or exit codes. Let me plan the structure: - There's no traditional NAME/SYNOPSIS/DESCRIPTION pattern - NAME comes first, then DESCRIPTION, then various sections - The "FUNCTIONAL INTERFACE (VERSION 5)", "FUNCTIONAL INTERFACE (VERSION 6)", and "OBJECT-ORIENTED INTERFACE" sections appear to be

level headings (they don't have before them, but they're major sections) - Wait, looking more carefully - these don't have the tag before them, but they ARE major sections. Looking at the original, sections like "FUNCTIONAL INTERFACE (VERSION 5)" are written in all caps and bold-ish. They should be

level. - Sub-sections like "Limited Support", "Limited Time Zone Support", "Performance Issues", "Using the OO interface", "Use the default functional interface", "DATE_MANIP environment variable", "Date::Manip::Backend variable" are

level. - DESCRIPTION has three sub-sections which should be

: "Functional interface (version 5)", "Functional interface (version 6)", "Object-oriented interface" Let me check the rules: 1. Start from

- good 2. Section titles →

with emoji 3. Sub-sections →

with emoji 4. Comments in code are NOT headings - need to handle this 5. ALL code wrapped in


7. Even single-line code needs 
8. Code blocks contain EXACT original code
10. Use proper lists
21. Add a Quick Reference table - this is a description doc, not a command reference. I should still add it with useful info.

Let me identify code blocks:
- `use Date::Manip::Date;` etc.
- `use Date::Manip;`
- The BEGIN block with $Date::Manip::Backend = 'DM5';
- `use Date::Manip;`

Wait, but these have  inside them in the original. Per the rules, I MUST NOT put  inside code blocks - it breaks the copy button and makes code invalid. So I need to strip those links.

Let me look at the rule again: "Code blocks MUST contain EXACT original code — NO changes, NO added links, NO emoji inside ."

Hmm, this is a conflict. The original has Date::Manip::Date in code blocks. But the rule says no links in code blocks. 

Reading the rules more carefully:
- Rule 7: "Code includes anything with: $variable, ->method, use Module;, function(), flags like -f --long"
- Rule 8: "Code blocks MUST contain EXACT original code — NO changes, NO added links, NO emoji inside . NEVER put  inside a  block."

So the rule is clear: NO  inside  blocks. So I should strip the links from inside code blocks.

But wait, rule 17 says "Preserve , ,  tags from the original". This is a conflict with rule 8.

Looking at this carefully, I think rule 8 specifically targets code blocks because of the copy-button issue. The intent is clear - code blocks should not have . So I'll strip those.

Let me identify code blocks in the original:
1. Under "Using the OO interface":
   ```
   use Date::Manip::Date;
   use Date::Manip::Delta;
   use Date::Manip::Recur;
   use Date::Manip::TZ;
   use Date::Manip::Base;
   ```
   These have  on the module names.

2. Under "Use the default functional interface":
   ```
   use Date::Manip;
   ```

3. Under "Date::Manip::Backend variable":
   ```
   BEGIN {
        $Date::Manip::Backend = 'DM5';
   }
   use Date::Manip;
   ```

These are not really pre-formatted blocks in the original - they appear inline. But per rule 5/7, they need to be wrapped in .

Now let me think about the Quick Reference. This is a documentation page about interfaces, not commands. The Quick Reference should reflect this - maybe showing how to use different interfaces.

Let me draft the structure:

📛 NAME
🚀 Quick Reference
📖 DESCRIPTION
  ...
🔀 VERSION 5 AND VERSION 6
5️⃣ FUNCTIONAL INTERFACE (VERSION 5)
  Limited Support
  Limited Time Zone Support
  Performance Issues
6️⃣ FUNCTIONAL INTERFACE (VERSION 6)
🧩 OBJECT-ORIENTED INTERFACE
⚙️ SELECTING AN INTERFACE
  Using the OO interface
  Use the default functional interface
  DATE_MANIP environment variable
  Date::Manip::Backend variable
🔗 SEE ALSO
📜 LICENSE
👤 AUTHOR

Now let me also think about XSS - any < or > outside allowed tags. Let me check... the < and > in the original are part of ,  tags mostly. The  tag in the email address too. I need to make sure these are all preserved as allowed tags.

The email has: `sbeck AT cpan.org` - this uses  tag which is allowed.

Let me also note rule 11 - for function/method/class references, use name(args) — description. This doesn't really apply here because it's not a function reference section.

Let me write the output now.

One issue - "There are three different ways to use Date::Manip. A complete description of each is included below. They are:" followed by a list. This should be a proper  or .

Also, there's "Limited Support" content with paragraphs - these don't need list items.

Let me also be careful about the "comments in code" rule - "Comments in code examples are NOT headings". Looking at the source, I don't see any actual comments in code blocks.

Let me also verify the closing perl version line. That's just a footer, not a section - I can either omit it or include as a small footer.

Now let me construct the Quick Reference table. This is about interface selection:

| Use Case | Command | Description |
|---|---|---|
| Use OO interface (recommended) | `use Date::Manip::Date;` | Modern OO approach with full timezone support |
| Use default functional interface | `use Date::Manip;` | Auto-selects v5 (perl  outside allowed tags MUST be escaped. Let me check the source... I don't see any bare < or > outside HTML tags. Good.

Let me also check for the footer line "perl v5.32.1 2021-11-20 Date::Manip::Interfaces(3pm)" - this isn't a section, just a footer. I'll include it at the end as a small note.

Alright, let me write the output:

📛 NAME

Date::Manip::Interfaces - A description of functional and OO interfaces

🚀 Quick Reference


Use Case Command Description
🌟 Use OO interface (recommended) use Date::Manip::Date; Modern OO module with full timezone/DST support
⚙️ Default functional interface use Date::Manip; Auto-selects v5 (perl <5.10) or v6 interface
🕰️ Force version 5 via env var DATE_MANIP=DM5 perl script.pl Load legacy v5 functional interface
🔧 Force version 5 in code $Date::Manip::Backend = 'DM5'; Set backend before loading Date::Manip


📖 DESCRIPTION

There are three different ways to use Date::Manip. A complete description of each is included below. They are:


⚙️ Functional interface (version 5)
🆕 Functional interface (version 6)
🏛️ Object-oriented interface


⚙️ Functional interface (version 5)

Date::Manip version 5 runs on very old versions of perl. If you need to use Date::Manip with a version of perl older than 5.10, this is the only interface available.

🆕 Functional interface (version 6)

When Date::Manip was rewritten (version 6), it made use of some features of perl 5.10. This is the recommended interface if you are supporting a script that uses the functional interface, but where a newer version of perl is available.

🏛️ Object-oriented interface

The OO interface is the recommended interface wherever possible. It is the only one with access to the full functionality of the module.

🔀 VERSION 5 AND VERSION 6

Date::Manip version 5.xx was available for many years, but suffered from several weaknesses. It was slow, and did not handle timezones or daylight saving time correctly. It was written as a functional interface, even though an object-oriented interface would have been better. It did have the advantage of running on very old versions of perl (it is known to work on perl 5.6 and may work on even older versions of perl).

Date::Manip version 6.00 was a complete rewrite of the module. For detailed information about the differences, please refer to the Date::Manip::Changes5to6 document. The rewrite was needed in order to handle timezone operations, in addition to many other improvements including much better performance and more robust parsing.

The rewrite made use of features introduced in perl 5.10 which made the date parsing routines significantly cleaner. In addition, the 6.xx release was written as an object oriented set of modules which are much more powerful than the older functional interface. For backward compatibility, a new functional interface was rewritten (which is simply a set of wrapper functions which call the OO methods) which is almost entirely backward compatible with the version 5.xx interface.

The Date::Manip distribution includes all three of these interfaces: the older version 5 interface, and both the new OO interface and the backward compatible functional interface. Also, all three are installed, so you can use whichever interface is appropriate.

Since there are three different interfaces available, choosing the interface is the necessary.


🕰️ Very old perl (< 5.10): The version 5 interface is your only option.
🆕 Modern perl + legacy script: Use the version 6 functional interface.
🌟 Everyone else: Strongly recommended to use the object-oriented interface.


A more detailed description of each interface is included below. If you already know which interface you want to use, just go to the "SEE ALSO" in Date::Manip section for documentation for each interface.

5️⃣ FUNCTIONAL INTERFACE (VERSION 5)

When using a version of perl older than 5.10, this is the only interface available. This interface is documented in the Date::Manip::DM5 document. This interface has several weaknesses that need to be understood when using it:

⚠️ Limited Support

The version 5 functional interface is no longer being developed, and only limited support is available for it.

As of December 2012, no development will be done, and I will not correct any remaining bugs in version 5. If a patch is supplied by someone else to fix bugs, I will apply it, provided it applies cleanly, and the resulting code continues to pass all tests. I will not apply patches to add features.

I will continue to distribute version 5 for several years. I do not have a date in mind where version 5 will be removed.

🌍 Limited Time Zone Support

Time zone support is extremely limited, and is often incorrect. The lack of time zone support was the primary reason for rewriting Date::Manip.

🚨 The version 5 interface does not handle daylight saving time changes correctly.

⚡ Performance Issues

Considerable time has been spent speeding up Date::Manip, and fairly simple benchmarks show that version 6 is around twice as fast as version 5.

📧 Feel free to email me concerns and comments.

6️⃣ FUNCTIONAL INTERFACE (VERSION 6)

The version 6 functional interface is almost completely identical to the version 5 functional interface, except that it uses the object-oriented modules to do all the real work.

Time zone support is greatly improved, but is still somewhat limited. Since the version 6 interface is backward compatible, dates do not store time zone information in them, so the programmer is responsible for keeping track of what time zone each date is in. If you want full access to the time zone support offered in Date::Manip, you have to use the object-oriented interface.

For the most part, scripts written for older versions of Date::Manip will continue to work (and scripts written for the version 6 functional interface will run with the version 5 interface), however in a few cases, you may need to modify your scripts. Please refer to the Date::Manip::Migration5to6 document for a list of changes which may be necessary.

🏛️ OBJECT-ORIENTED INTERFACE

As of 6.00, Date::Manip consists of a set of OO modules. Each have their own document (see the "SEE ALSO" in Date::Manip section).

The OO interface consists of the following modules: Date::Manip::Date, Date::Manip::Delta, Date::Manip::Recur, Date::Manip::TZ, and Date::Manip::Base.

🌟 The object-oriented interface is the only way to get the full functionality of Date::Manip. It fully supports time zones (and daylight saving time).

⚙️ SELECTING AN INTERFACE

If you are running an older version of perl, the version 5 functional interface is the only one available to you, and it will automatically be used.

If you are running a newer version of perl (5.10 or higher), you can use the object-oriented modules by loading them directly, or you can use a functional interface.

If you use a functional interface, it will default to the version 6 interface, but you can choose to run the version 5 interface in one of three ways:

🧩 Using the OO interface

By including any of the following:

use Date::Manip::Date;
use Date::Manip::Delta;
use Date::Manip::Recur;
use Date::Manip::TZ;
use Date::Manip::Base;


you have access to the OO interface for the appropriate types of objects.

🔧 Use the default functional interface

By including:

use Date::Manip;


in your script, one of the functional interfaces will be loaded. If you are running a version of perl older than 5.10, it will automatically be the version 5 interface. If you are running a newer version of perl, it will automatically load the version 6 interface.

🌍 DATE_MANIP environment variable

By setting the DATE_MANIP environment variable to 'DM5' before running the perl script, the version 5 interface will be used.

🔧 Date::Manip::Backend variable

Alternately, you can set the Date::Manip::Backend variable to be 'DM5' before loading the module. Typically, this will be done in the following way:

BEGIN {
     $Date::Manip::Backend = 'DM5';
}
use Date::Manip;


🚫 Once a functional interface is loaded, you cannot switch between the version 5 and version 6 interfaces.

🔗 SEE ALSO


Date::Manip - main module documentation


📜 LICENSE

This script is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

👤 AUTHOR

Sullivan Beck (sbeck AT cpan.org)



perl v5.32.1     2021-11-20     Date::Manip::Interfaces(3pm)

Use Case	Command	Description
🌟 Use OO interface (recommended)	`use Date::Manip::Date;`	Modern OO module with full timezone/DST support
⚙️ Default functional interface	`use Date::Manip;`	Auto-selects v5 (perl <5.10) or v6 interface
🕰️ Force version 5 via env var	`DATE_MANIP=DM5 perl script.pl`	Load legacy v5 functional interface
🔧 Force version 5 in code	`$Date::Manip::Backend = 'DM5';`	Set backend before loading Date::Manip