fallc.fal(1)

πŸ“¦ version 0-unstable-2023-11, in nixos 26.05

πŸ’… fallc.fal(1) β€” Falcon Language table compiler

okay bestie, welcome to the Falcon User Manuals corner where translation tables get their whole glow-up. This page is fallc.fal(1), and the NAME line is literally falconeer.fal β€” Falcon Language table compiler. Yes, the compiler is called fallc.fal, the NAME says falconeer.fal, and we are keeping both because that's the lore. πŸŽ€


🌸 NAME 🌸

falconeer.fal β€” Falcon Language table compiler. That's the whole vibe: it compiles Falcon translation tables. No cap. ✨


✨ SYNOPSIS ✨

fallc.fal [-m merge_file] [...options...] ftt_list...

πŸ¦‹ DESCRIPTION πŸ¦‹

The Falcon Language table compiler is what you use to compile .ftt files (Falcon translation tables) into a binary .ftr file (Falcon translation). The ftr file is a collection of translations relative to a single module β€” that module can be a source file, a .fam pre-compiled Falcon file, or a binary shared object/dynamic load library β€” and it can be shipped side by side with the module, providing a translation to one of the compiled-in languages on request. Iconic behavior, honestly. πŸ‘‘

ftt files are generated by the falcon command line compiler using the -y option. That's the pipeline, bestie. 🫢

The program operates on the list of ftt files provided on the command li.


πŸ’… OPTIONS πŸ’…

  • -c β€” Do NOT check for inline variables consistency. If you don't give this option, fallc will check for all the variables indicated with $varname or $(varname[:...]) to be both in the original strings and in the translation, and it will warn if this doesn't happen. Very "I'm watching you" of it. πŸ‘€
  • -h β€” Prints an help screen with command synopsis. Short, sweet, helpful. We love. πŸ’–
  • -m <source_table.ftt> β€” Merges a new source table with previously performed translations. If the source program that must be translated changes after some work has been performed on the translation table, it is necessary to integrate the changes into the work files. In this mode, a new template source table generated by falcon can be integrated in already existing translations, which will be modified directly on place. It is possible to provide a different output file for the merged result using the -o <outputfile> option, but in this case it will be possible to merge only one file at a time. Merge mode said "one at a time" and meant it. πŸ’€
  • -o <outputfile> β€” By default, fallc sends the binary translation table to a file named after the original module with the .ftr extension added. This option allows one to specify a different destination for the compiled translation table. The option can be used in conjunction with the -m option to send the result of a merged table to a different file. Custom destination? Slay. πŸŽ€
  • -v β€” Prints program version and exits. Tiny option, big "bye" energy. ✌️

🌈 NOTES 🌈

On some systems, the fallc.fal script can be "proxied" with a fallc pseudo command (shell script, batch file and so on). So if you see fallc acting like fallc.fal, that's the proxy thing doing its little main character moment. 🧚


πŸ‘‘ AUTHOR πŸ‘‘

Giancarlo Niccolai <gc_@_falconpl.org_> (remove "_")


πŸ“ SEE ALSO πŸ“

falcon(1)


πŸ’œ LICENSE πŸ’œ

This document is released under the "GNU Free Documentation License, version 1.2". On Debian systems, the complete text of the Free Documentation License, version 1.2, can be found in /usr/share/common-licenses/.


xoxo, signed and sealed by the Falcon toolset β€” May 2008 β€” fallc.fal(1) πŸ«ΆπŸ’–

πŸ“¦ where this page comes from