Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for Conventions (3.02 sec)

  1. doc/go1.17_spec.html

    	_    [4]byte "ceci n'est pas un champ de structure"
    }
    
    // A struct corresponding to a TimeStamp protocol buffer.
    // The tag strings define the protocol buffer field numbers;
    // they follow the convention outlined by the reflect package.
    struct {
    	microsec  uint64 `protobuf:"1"`
    	serverIP6 uint64 `protobuf:"2"`
    }
    </pre>
    
    <h3 id="Pointer_types">Pointer types</h3>
    
    <p>
    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)
  2. doc/asm.html

    (The meaning of the offset—offset from the frame pointer—distinct
    from its use with <code>SB</code>, where it is an offset from the symbol.)
    The assembler enforces this convention, rejecting plain <code>0(FP)</code> and <code>8(FP)</code>.
    The actual name is semantically irrelevant but should be used to document
    the argument's name.
    It is worth stressing that <code>FP</code> is always a
    HTML
    - Registered: Tue May 07 11:14:38 GMT 2024
    - Last Modified: Tue Nov 28 19:15:27 GMT 2023
    - 36.3K bytes
    - Viewed (0)
  3. doc/go_spec.html

    	_    [4]byte "ceci n'est pas un champ de structure"
    }
    
    // A struct corresponding to a TimeStamp protocol buffer.
    // The tag strings define the protocol buffer field numbers;
    // they follow the convention outlined by the reflect package.
    struct {
    	microsec  uint64 `protobuf:"1"`
    	serverIP6 uint64 `protobuf:"2"`
    }
    </pre>
    
    <p>
    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