


Why does the problem of result accumulation occur when using callback functions in Foreach loops? How to solve it?
The cumulative problem and solution of callback functions in foreach
loop
This article discusses the cumulative result problems that may arise when using callback functions in foreach
loops and provides corresponding solutions.
Problem description
When using foreach
loop to iterate over the data and call the callback function getchildareaid
to get the sub-region ID, it is found that the results are accumulated. The code is as follows:
foreach ($towns as $key => $val) { $areaidarr = getchildareaid($val['id']); $result[$val['name']] = $worker::where('area_id', 'in', $areaidarr)->count(); }
The callback function getchildareaid
is defined as follows:
function getchildaiid($id) { static $area; $area = $area ?? new \app\common\model\area; $result = collection($area->where(['pid' => $id])->order('id desc')->select())->toArray(); static $res = []; if ($result) { foreach ($result as $key => $val) { $res[] = $val['id']; getchildareaiid($val['id']); } } return $res; }
The problem is that the getchildareaid
function uses the static variable $res
, which causes the previous result to accumulate every time it is called, rather than to calculate independently each time.
Problem analysis
static $res = [];
declares a static variable in getchildareaid
function. Static variables will not be destroyed after the function call is finished, and their values will be retained in subsequent calls. Therefore, every time foreach
loop calls getchildareaid
, $res
accumulates new results, which eventually leads to an error in the result.
Solution
To solve this problem and avoid using static variables, the following two methods can be used:
Rewrite the function, use local variables: Create a new function, instead of using the static variable
$res
, but use local variables to store the results of each call.Modify existing functions and eliminate static variables: Modify
getchildareaid
function, remove static variable$res
, and return a new array when called recursively to avoid the accumulation of results. The modified function is as follows:
function getChildAreaId($id) { $area = new \app\common\model\Area; $result = collection($area->where(['pid' => $id])->order('id desc')->select())->toArray(); $res = []; if ($result) { foreach ($result as $key => $val) { $res[] = $val['id']; $res = array_merge($res, getChildAreaId($val['id'])); } } return $res; }
This modified function creates a new $res
array every time it is called recursively and merges the recursive results into the current $res
, thus avoiding the problem of result accumulation. Which solution to choose depends on the overall structure and maintainability of the code. Usually, rewriting functions is clearer and easier to understand.
Through the above methods, the problem of callback function results accumulation in foreach
loop can be effectively solved, ensuring that the correct result can be obtained every time the callback function is called.
The above is the detailed content of Why does the problem of result accumulation occur when using callback functions in Foreach loops? How to solve it?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











DMA in C refers to DirectMemoryAccess, a direct memory access technology, allowing hardware devices to directly transmit data to memory without CPU intervention. 1) DMA operation is highly dependent on hardware devices and drivers, and the implementation method varies from system to system. 2) Direct access to memory may bring security risks, and the correctness and security of the code must be ensured. 3) DMA can improve performance, but improper use may lead to degradation of system performance. Through practice and learning, we can master the skills of using DMA and maximize its effectiveness in scenarios such as high-speed data transmission and real-time signal processing.

Using the chrono library in C can allow you to control time and time intervals more accurately. Let's explore the charm of this library. C's chrono library is part of the standard library, which provides a modern way to deal with time and time intervals. For programmers who have suffered from time.h and ctime, chrono is undoubtedly a boon. It not only improves the readability and maintainability of the code, but also provides higher accuracy and flexibility. Let's start with the basics. The chrono library mainly includes the following key components: std::chrono::system_clock: represents the system clock, used to obtain the current time. std::chron

Efficient methods for batch inserting data in MySQL include: 1. Using INSERTINTO...VALUES syntax, 2. Using LOADDATAINFILE command, 3. Using transaction processing, 4. Adjust batch size, 5. Disable indexing, 6. Using INSERTIGNORE or INSERT...ONDUPLICATEKEYUPDATE, these methods can significantly improve database operation efficiency.

Measuring thread performance in C can use the timing tools, performance analysis tools, and custom timers in the standard library. 1. Use the library to measure execution time. 2. Use gprof for performance analysis. The steps include adding the -pg option during compilation, running the program to generate a gmon.out file, and generating a performance report. 3. Use Valgrind's Callgrind module to perform more detailed analysis. The steps include running the program to generate the callgrind.out file and viewing the results using kcachegrind. 4. Custom timers can flexibly measure the execution time of a specific code segment. These methods help to fully understand thread performance and optimize code.

Handling high DPI display in C can be achieved through the following steps: 1) Understand DPI and scaling, use the operating system API to obtain DPI information and adjust the graphics output; 2) Handle cross-platform compatibility, use cross-platform graphics libraries such as SDL or Qt; 3) Perform performance optimization, improve performance through cache, hardware acceleration, and dynamic adjustment of the details level; 4) Solve common problems, such as blurred text and interface elements are too small, and solve by correctly applying DPI scaling.

C performs well in real-time operating system (RTOS) programming, providing efficient execution efficiency and precise time management. 1) C Meet the needs of RTOS through direct operation of hardware resources and efficient memory management. 2) Using object-oriented features, C can design a flexible task scheduling system. 3) C supports efficient interrupt processing, but dynamic memory allocation and exception processing must be avoided to ensure real-time. 4) Template programming and inline functions help in performance optimization. 5) In practical applications, C can be used to implement an efficient logging system.

The main differences between Laravel and Yii are design concepts, functional characteristics and usage scenarios. 1.Laravel focuses on the simplicity and pleasure of development, and provides rich functions such as EloquentORM and Artisan tools, suitable for rapid development and beginners. 2.Yii emphasizes performance and efficiency, is suitable for high-load applications, and provides efficient ActiveRecord and cache systems, but has a steep learning curve.

MySQL functions can be used for data processing and calculation. 1. Basic usage includes string processing, date calculation and mathematical operations. 2. Advanced usage involves combining multiple functions to implement complex operations. 3. Performance optimization requires avoiding the use of functions in the WHERE clause and using GROUPBY and temporary tables.
