- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for practices (0.26 sec)
-
src/cmd/cgo/doc.go
identifiers not by parsing C code but by feeding carefully constructed programs into the system C compiler and interpreting the generated error messages, debug information, and object files. In practice, parsing these is significantly less work and more robust than parsing C source. Cgo first invokes gcc -E -dM on the preamble, in order to find out about simple #defines for constants and the like. These are recorded
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) -
src/cmd/asm/internal/asm/parse.go
return 0 } return uint16(reg) } // Note: There are two changes in the expression handling here // compared to the old yacc/C implementations. Neither has // much practical consequence because the expressions we // see in assembly code are simple, but for the record: // // 1) Evaluation uses uint64; the old one used int64. // 2) Precedence uses Go rules not C rules.
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Feb 21 14:34:57 GMT 2024 - 36.9K bytes - Viewed (0) -
src/archive/tar/writer_test.go
t.Fatal(err) } hdr, err := FileInfoHeader(fileinfo, "") if err != nil { t.Fatalf("os.Stat:1 %v", err) } hdr.Typeflag = TypeDir // Force a PAX long name to be written. The name was taken from a practical example // that fails and replaced ever char through numbers to anonymize the sample.
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Feb 27 16:39:23 GMT 2024 - 38.7K bytes - Viewed (0)