n/ziglings
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

some improvements in the description

Browse source
This commit is contained in:
Chris Boesch 2023-02-16 19:28:10 +01:00
parent bb95625477
commit dc187889c1
2 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
build.zig
View file

@ -465,14 +465,14 @@ const exercises = [_]Exercise{
// .output = "ABCDEF",
// .@"async" = true,
// },
.{
.main_file = "092_interfaces.zig",
.output = "Daily Insect Report:\nAnt is alive.\nBee visited 17 flowers.\nGrasshopper hopped 32 meters.",
},
.{
.main_file = "093_hello_c.zig",
.output = "Hello C from Zig! - C result ist 17 chars",
.C = true,
},
.{
.main_file = "092_interfaces.zig",
.output = "Daily Insect Report:\nAnt is alive.\nBee visited 17 flowers.\nGrasshopper hopped 32 meters.",
},
.{
.main_file = "999_the_end.zig",

8
exercises/093_hello_c.zig
View file

@ -36,11 +36,11 @@
//
// So that all this does not remain a dry theroy now, let's just start
// and call a C function out of Zig.
//
// our well-known "import" for Zig
const std = @import("std");
// new the import for C
// and here the new the import for C
const c = @cImport({
@cInclude("unistd.h");
});
@ -50,9 +50,9 @@ pub fn main() void {
// In order to output a text that can be evaluated by the
// Zig Builder, we need to write it to the Error output.
// In Zig we do this with "std.debug.print" and in C we can
// specify the file descriptor i.e. 2 for error console.
// specify a file descriptor i.e. 2 for error console.
//
// In this case we use 'write' to output 17 chars,
// In this exercise we use 'write' to output 17 chars,
// but something is missing...
const c_res = write(2, "Hello C from Zig!", 17);