dongyong9224 2018-09-28 19:58
浏览 15


I see a lot of codes like this in the golang src:

func Open(path string) (*Plugin, error) {
    return open(path)

func open() {
  // etc

A private function been called from a public. Why not just:

func Open(path string) (*Plugin, error) {
    // code of open here


I do understand that sometimes it makes sense, especially if there are more functions using open. But that's not the case.

Is this some kind of Golang way of organizing things?

  • 写回答

1条回答 默认 最新

  • douhan9191 2018-09-28 20:09

    In this case, it appears to be because the actual implementation is OS dependent.

    The plugin implementation plugin_dlopen.go is used only for OSX and Linux, and the alternative plugin_stubs.go is for everything else(which just contains dummy functions as there is no implementation for other systems yet.)

    This allows you to keep OS dependent code in one file using build tags, while keeping general code, the public API and documentation for the public API in a single place.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?



  • ¥20 simulink中怎么使用solve函数?
  • ¥30 dspbuilder中使用signalcompiler时报错Error during compilation: Fitter failed,求解决办法
  • ¥15 gwas 分析-数据质控之过滤稀有突变中出现的问题
  • ¥15 没有注册类 (异常来自 HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
  • ¥15 知识蒸馏实战博客问题
  • ¥15 用PLC设计纸袋糊底机送料系统
  • ¥15 simulink仿真中dtc控制永磁同步电机如何控制开关频率
  • ¥15 用C语言输入方程怎么
  • ¥15 网站显示不安全连接问题
  • ¥15 51单片机显示器问题