#includes and processing the corresponding C code. That would require
a full C parser and type checker that was also aware of any extensions
known to the system compiler (for example, all the GNU C extensions) as
well as the system-specific header locations and system-specific
pre-#defined macros. This is certainly possible to do, but it is an
enormous amount of work.

Cgo takes a different approach. It determines the meaning of C

* the data from the client to be sent through the network
* the data sent by your program to be received by the client through the network
* the contents of a file in the disk to be read by the system and given to your program
* the contents your program gave to the system to be written to disk
* a remote API operation
* a database operation to finish
* a database query to return the results
* etc.

	user, exists := globalIAMSys.GetUser(ctx, accessKey)
	if exists && (user.Credentials.IsTemp() || user.Credentials.IsServiceAccount()) {
		// Updating STS credential is not allowed, and this API does not
		// support updating service accounts.
		writeErrorResponseJSON(ctx, w, errorCodes.ToAPIErr(ErrAddUserInvalidArgument), r.URL)
		return
	}

	if (cred.IsTemp() || cred.IsServiceAccount()) && cred.ParentUser == accessKey {

        System.setProperty("test_var", "underscore");
        value = "${test_var}";
        assertEquals("underscore", ResourceUtil.resolve(value));

        // Clean up test properties
        System.clearProperty("var1");
        System.clearProperty("var2");
        System.clearProperty("special");
        System.clearProperty("123");
        System.clearProperty("test_var");
    }

    System.out.printf("%.2f Executing call.%n", (System.nanoTime() - startNanos) / 1e9f);
    try (Response response = call.execute()) {
      System.out.printf("%.2f Call was expected to fail, but completed: %s%n",
          (System.nanoTime() - startNanos) / 1e9f, response);
    } catch (IOException e) {
      System.out.printf("%.2f Call failed as expected: %s%n",
          (System.nanoTime() - startNanos) / 1e9f, e);
    }
  }

            }

            // The temporary file is named destination + ".tmp" and is done this way to ensure
            // that the temporary file is in the same file system as the destination because the
            // File.renameTo operation doesn't really work across file systems.
            // So we will attempt to do a File.renameTo for efficiency and atomicity, if this fails

 */
package jcifs.internal.fscc;

import jcifs.Decodable;

/**
 * Base interface for File System Control Code (FSCC) file system information structures.
 * Provides common functionality for various SMB2/SMB3 file system information classes
 * used in query file system information operations, with constants for information levels.
 *
 * @author mbechler
 */

    * All this would also work for deeply nested JSON objects.
* Convert from and to JSON automatically.
* Document everything with OpenAPI, that can be used by:
    * Interactive documentation systems.
    * Automatic client code generation systems, for many languages.
* Provide 2 interactive documentation web interfaces directly.

---

We just scratched the surface, but you already get the idea of how it all works.

        File lmhostsFile = tempDir.resolve("lmhosts").toFile();
        lmhostsFile.createNewFile();

        // Make file unreadable on Unix-like systems
        boolean isWindows = System.getProperty("os.name").toLowerCase().contains("windows");
        if (!isWindows) {
            assertTrue(lmhostsFile.setReadable(false));
        }

        // This test verifies that the handler resolution mechanism correctly skips the 'jcifs'
        // package when it is listed in the 'java.protocol.handler.pkgs' system property.
        // We use mock handlers since actual system handlers might not be available in test environment.
        System.setProperty("java.protocol.handler.pkgs", "jcifs");
        setupMockProtocolHandlers();
        URL url = new URL("http://example.com/resource");