slice2cs(1)

πŸ“¦
version 3.7.10 Β· 2 versions
, in arch rolling, debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute

πŸ’– slice2cs β€” the Slice to C# compiler πŸ’–

okay bestie, gather round, because this is the manual page for slice2cs(1) from the General Commands Manual, and she is literally the moment. ✨


🌸 NAME 🌸

slice2cs β€” the Slice to C# compiler. that's it, that's the girl. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

slice2cs [options] [files]

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the tea: slice2cs compiles Slice files into C#. no cap, that's the whole job. 🫢

and bestie, listen β€” the macro __SLICE2CS__ gets defined while this compilation is happening. so if your Slice files are checking for it, she's there. iconic behavior. πŸ‘‘

The full documentation for slice2cs lives online at:

https://doc.zeroc.com/ice/3.7/language-mappings/c-sharp-mapping/client-side-slice-to-c-sharp-mapping/slice2cs-command-line-options

like, go read it if you want the deep lore. πŸ“š


✨ OPTIONS ✨

every single one, no skipping, no summarizing, we respect the flag list in this house πŸ πŸ’–

  • -h, --help β€” shows you a help message. the classic "what do I even do here" button.
  • -v, --version β€” prints the compiler version. vibe check on which build you're running. ⭐
  • -DNAME β€” defines the preprocessor symbol NAME. boom, she exists now.
  • -DNAME=DEF β€” defines the preprocessor symbol NAME and gives it the value DEF. now she has lore.
  • -UNAME β€” undefines the preprocessor symbol NAME. not me erasing her entire existence 😭
  • -IDIR β€” adds the directory DIR to the search path for #include directives. she's out here networking 🌈
  • -E β€” prints the preprocessor output on stdout. raw, unfiltered, pre-processed. πŸ“
  • --output-dir DIR β€” puts the generated files into directory DIR. everything goes in this folder, periodt.
  • -d, --debug β€” prints debug information showing the operation of the Slice parser. she's telling you everything she's doing, like a group chat at 2am πŸ’€
  • --depend β€” prints dependency information to standard output by default, or to the file specified by the --depend-file option. and listen: no code is generated when this option is specified. zero. none. just the deps.
  • --depend-xml β€” same energy but the dependency information comes out in XML format, to standard output by default or to the file specified by --depend-file. and again, no code is generated when this option is specified. 🧚
  • --depend-file FILE β€” sends dependency information to the specified file. which format you get depends on whether --depend or --depend-xml is also specified. they're a package deal, iykyk.
  • --validate β€” checks the command-line options you provided for correctness and does not generate any code. it's just a vibe check, no output. πŸ™ˆ
  • --tie β€” generates tie classes. slay. πŸŽ€
  • --impl β€” generates sample implementation files. heads up bestie: this option will not overwrite an existing file. she's respectful like that. πŸ’œ
  • --impl-tie β€” generates sample implementation files using tie classes. and same rule: this option will not overwrite an existing file. 🫢
  • --checksum CLASS β€” generates checksums for Slice definitions. math but make it fashion. ✨
fr fr, if you're reaching for --depend or --depend-xml, don't expect code out the other end. that's not a bug, that's the design, bestie. πŸ’€

🌈 SEE ALSO 🌈

the whole sibling squad, go say hi:


and that's the whole page, bestie! 🫢 this was slice2cs(1) from the General Commands Manual β€” you just read the entire thing, main character energy fr fr. go compile something gorgeous. πŸ’–βœ¨πŸŽ€