slice2cs(1)

💖 slice2cs(1) — the Slice ➡️ C# compiler, bestie edition 💅

Okay so real talk: this page is from the General Commands Manual, and the command we're hyping up is slice2cs — the Slice to C# compiler. Grab a strawberry 🍓, sit down, and let's get into it.

---

✨ NAME ✨

slice2cs — the Slice to C# compiler. That's it, that's the name, periodt. 👑

---

🌈 SYNOPSIS 🌈

slice2swift [options] [files]

Bestie. I know. I KNOW. 💀 The synopsis says slice2swift, not slice2cs. I'm not editing it, I'm not "fixing" it, I'm just showing you the receipt exactly as it was handed to me. It's giving typo energy, and we're all just living in it. 🙈 Anyway: options, then files. That's the shape of it.

---

🦋 DESCRIPTION 🦋

So slice2swift compiles Slice files to Swift. During this compilation the macro __SLICE2SWIFT__ is defined. Yes, again — this is the Swift one being described, on the C# page. I am simply the messenger and the messenger is sipping her drink. 🧚

The full documentation for slice2swift is available online at:

https://doc.zeroc.com/ice/latest/language-mappings/swift-mapping/client-side-slice-to-swift-mapping/slice2swift-command-line-options

Lowkey a whole novel over there, but it's the official source so go off. ✨

---

💅 OPTIONS 💅

Alright, the main event. Every single flag, no skips, no "eh you get the idea". You get the idea and the flag. 🫶

• -h, --help — shows you a help message. Your little rescue blanket when you forget everything. 🌸
• -v, --version — prints out the compiler version. Vibe check the build. ⭐
• -DNAME — defines the preprocessor symbol NAME. Manifesting it into existence. ✨
• -DNAME=DEF — defines the preprocessor symbol NAME and gives it the value DEF. Now it's got lore. 📖
• -UNAME — undefines the preprocessor symbol NAME. Unmanifesting. Not every symbol gets to stay. 💀
• -IDIR — adds the directory DIR to the search path for #include directives. It's the "where do I look for my friends" option. 🫶
• -E — prints the preprocessor output on stdout. Just the preprocessed tea, no compiling, no code gen. ☕
• --output-dir DIR — drops the generated files into directory DIR. Giving your files a home. 🏠
• -d, --debug — prints debug information showing the operation of the Slice parser. Not me peeking behind the curtain to watch the parser work 🔍
• --depend — prints dependency information to standard output by default, or to the file named by the --depend-file option. Heads up bestie: no code is generated when this option is specified.
• --depend-xml — prints dependency information in XML format, to standard output by default, or to the file named by the --depend-file option. Also: no code is generated when this option is specified. Same rules, fancier format. 💖
• --depend-file FILE — sends the dependency information into the specified file. Which format you get depends on whether --depend or --depend-xml is also specified. 👀
• --validate — checks that the command-line options you gave are correct, and does not generate any code. The "am I doing this right" button. ✅

Reminder to my girlies: --depend, --depend-xml and --validate all mean no code gets generated. If you're sitting there wondering where your output files went... that's why. 😭

---

🔥 SEE ALSO 🔥

The whole Slice compiler friend group, all together, all iconic:

• slice2cpp(1)
• slice2cs(1)
• slice2java(1)
• slice2js(1)
• slice2matlab(1)
• slice2objc(1)
• slice2php(1)
• slice2py(1)
• slice2rb(1)

Squad goals fr fr. 🌈

---

And that's the whole page, babes. This was slice2cs(1) from the General Commands Manual — shoutout to the manpage itself for carrying all this info, and to you for reading the entire thing instead of just scrolling to the flags. Main character behavior. No cap. 💖✨🎀