Avoid Calendar class use

Docs > Code Analysis > Static Analysis Rules > Avoid Calendar class use

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Metadata

ID: java-best-practices/avoid-calendar-creation

Language: Java

Severity: Warning

Category: Best Practices

Description

Creating instances of java.util.Calendar is expensive. Use alternatives that are less heavy and better in terms of performance.

Non-Compliant Code Examples

public class Main {
    public static void main(String[] args) {
        Date d = Calendar.getInstance().getTime();
        long ms = Calendar.getInstance().getTimeInMillis();
    }
}

Compliant Code Examples

public class Main {
    public static void main(String[] args) {
        Date d = new Date();
        long ms = System.currentTimeMillis();
    }
}

How to use this rule

1
2
rulesets:
  - java-best-practices     # Rules to enforce Java best practices.

Create a static-analysis.datadog.yml with the content above at the root of your repository
Use our free IDE Plugins or add Code Analysis scans to your CI pipelines
Get feedback on your code

For more information, please read the Code Analysis documentation

VS Code Extension

Identify code vulnerabilities directly in your
VS Code editor

JetBrains Plugin

Identify code vulnerabilities directly in
JetBrains products