


Why can't I call the server method directly instead of just adding intermediate variables?
In PHP, why can't we call the server method directly instead of just adding intermediate variables? This is a common question. PHP editor Apple will answer it for you. In PHP, we usually use front-end pages to interact with back-end servers. Directly calling server methods may involve some security risks, such as being used by hackers to perform malicious operations. To increase security, we introduce the concept of intermediate variables. By sending the front-end request to the server, and the server then performs corresponding operations based on the value of the intermediate variable, potential security risks can be effectively reduced. In addition, using intermediate variables can also increase the maintainability and scalability of the code, making the code clearer and easier to understand. In summary, adding intermediate variables is a safe and reliable practice that can improve the quality and reliability of your code.
Question content
I am writing a client for mqtt. I wrote a callback for mqtt.OnConnectHandler. I want to write the connection address of the print server.
var connectHandler mqtt.OnConnectHandler = func(c mqtt.Client) { // this is ok options := c.OptionsReader() s := options.Servers() fmt.Printf("conn: %s success\n", s) // -------------------------------------- // But it won't work like this // here have error: On servers。 // cannot call pointer method Servers on mqtt.ClientOptionsReadercompilerInvalidMethodExpr o := c.OptionsReader().Servers() fmt.Printf("conn: %s success\n", o) }
So, I found that I can't use it directly. Why? Aren't they the same thing? Why can only intermediate variables be used to receive?
I tried two methods. You only succeed once. I thought both would be fine.
Solution
This is because the Servers
method is declared with a pointer receiver. This means that in order to call Servers
, the receiver must be addressable:
https://www.php.cn/link/753a043674f0193523abc1bbce678686
Temporary variables are not addressable. here:
c.OptionsReader().Servers()
c.OptionsReader()
returns an unaddressable value, so you cannot call Servers
with that value as the receiver. When you assign the return value of c.OptionsReader
to a variable, it becomes addressable, and you can call Servers()
with that variable.
The above is the detailed content of Why can't I call the server method directly instead of just adding intermediate variables?. 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

AI Hentai Generator
Generate AI Hentai for free.

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

This article explains Go's package import mechanisms: named imports (e.g., import "fmt") and blank imports (e.g., import _ "fmt"). Named imports make package contents accessible, while blank imports only execute t

This article details efficient conversion of MySQL query results into Go struct slices. It emphasizes using database/sql's Scan method for optimal performance, avoiding manual parsing. Best practices for struct field mapping using db tags and robus

This article explains Beego's NewFlash() function for inter-page data transfer in web applications. It focuses on using NewFlash() to display temporary messages (success, error, warning) between controllers, leveraging the session mechanism. Limita

This article explores Go's custom type constraints for generics. It details how interfaces define minimum type requirements for generic functions, improving type safety and code reusability. The article also discusses limitations and best practices

This article demonstrates creating mocks and stubs in Go for unit testing. It emphasizes using interfaces, provides examples of mock implementations, and discusses best practices like keeping mocks focused and using assertion libraries. The articl

This article details efficient file writing in Go, comparing os.WriteFile (suitable for small files) with os.OpenFile and buffered writes (optimal for large files). It emphasizes robust error handling, using defer, and checking for specific errors.

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

This article explores using tracing tools to analyze Go application execution flow. It discusses manual and automatic instrumentation techniques, comparing tools like Jaeger, Zipkin, and OpenTelemetry, and highlighting effective data visualization
