Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for tablet (0.23 sec)

  1. src/cmd/cgo/doc.go

    use. You can do this by setting the generic CC_FOR_TARGET or the
    more specific CC_FOR_${GOOS}_${GOARCH} (for example, CC_FOR_linux_arm)
    environment variable when building the toolchain using make.bash,
    or you can set the CC environment variable any time you run the go tool.
    
    The CXX_FOR_TARGET, CXX_FOR_${GOOS}_${GOARCH}, and CXX
    environment variables work in a similar way for C++ code.
    
    Go
    - Registered: Tue Apr 30 11:13:12 GMT 2024
    - Last Modified: Sun Mar 31 09:02:45 GMT 2024
    - 42.1K bytes
    - Viewed (0)
  2. doc/go1.17_spec.html

    Assume we have compiled a package containing the package clause
    <code>package math</code>, which exports function <code>Sin</code>, and
    installed the compiled package in the file identified by
    <code>"lib/math"</code>.
    This table illustrates how <code>Sin</code> is accessed in files
    that import the package after the
    various types of import declaration.
    </p>
    
    <pre class="grammar">
    Import declaration          Local name of Sin
    
    HTML
    - Registered: Tue May 07 11:14:38 GMT 2024
    - Last Modified: Thu Apr 11 20:22:45 GMT 2024
    - 211.6K bytes
    - Viewed (0)
  3. doc/go_spec.html

    Consider a compiled a package containing the package clause
    <code>package math</code>, which exports function <code>Sin</code>, and
    installed the compiled package in the file identified by
    <code>"lib/math"</code>.
    This table illustrates how <code>Sin</code> is accessed in files
    that import the package after the
    various types of import declaration.
    </p>
    
    <pre class="grammar">
    Import declaration          Local name of Sin
    
    HTML
    - Registered: Tue May 07 11:14:38 GMT 2024
    - Last Modified: Thu May 02 22:43:51 GMT 2024
    - 279.6K bytes
    - Viewed (0)
Back to top