WordPress.org

Make WordPress Core

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#6021 closed enhancement (invalid)

Use the "@" modifier sparingly (or not at all).

Reported by: orlandu63 Owned by: jacobsantos
Milestone: Priority: lowest
Severity: trivial Version: 2.3.3
Component: Optimization Keywords:
Focuses: Cc:

Description

The "@" error-control operator should be avoided. It is slow.

In /wp-includes/script-loader.php you can use array_pad(func_get_args(), 4, null) to achieve the same effect (and save a few CPU cycles). I just noticed this while browsing recent changesets, so I'm sure there are more potential @-replacements out there.

Change History (5)

#1 @orlandu63
10 years ago

  • Milestone changed from 2.3.4 to 2.7
  • Version set to 2.3.3

#2 @orlandu63
10 years ago

  • Milestone changed from 2.7 to 2.6

#3 @santosj
10 years ago

  • Owner changed from anonymous to jacobsantos

#4 @jacobsantos
10 years ago

  • Milestone 2.9 deleted
  • Resolution set to invalid
  • Status changed from new to closed

It is difficult to go through and correct all of the instances where '@' is used, because sometimes it is used to prevent warnings that can't be checked before hand.

#5 @jacobsantos
10 years ago

It is better to be safe than sorry when it comes to accidentally displaying warnings and notices for blogs that don't want it.

Note: See TracTickets for help on using tickets.