SHILKA(1)

💖 NAME 💖

okay bestie, this is shilka — the keywords description translator — and you're reading the SHILKA(1) manual page 💅✨

---

✨ SYNOPSIS ✨

shilka [ -c++ --statistics -inline -strip -length -case -no-definitions
-interface -export -enum -pprefix -time -fast n -w -h -help -v]
specification-file

---

🌸 DESCRIPTION 🌸

So SHILKA generates code for fast recognition of pipeline hazards of a processor that's described in the specification file. The specification file must have the suffix .shilka 🎀

The generated code consists of optional interface and implementation files having the same names as one of the specification file and correspondingly suffixes .h (if option -interface is given) and .c (C code) or .cpp (C++ code) 🦋

The fast recognition of keywords is based on a structure called as minimal prunned O-trie. Full documentation of SHILKA is in the SHILKA User's manual 📚

---

💅 OPTIONS 💅

The options which are known for SHILKA are:

• -c++ — output of C++ code instead of C code (which is the default). 🔥
• -statistics — generation of a macro definition which switches on gathering and printing keyword occurrence statistics. Then those statistics can be used for setting up frequencies in the description file for faster recognition of keywords ✨
• -inline — generation of the function of keyword recognition as inline (take care with the used C compiler). This can speed up keyword recognition 💨
• -strip — striping off code for gathering and printing statistics. By default the code is present in the implementation file. The code can be switched on by definition of a macro (see option -statistics) 🫶
• -length — usage of strncmp instead of strcmp to compare keywords. This can be useful if the keyword is represented by a string without the C string end marker (' ') 🎀
• -case — keywords case is ignored during their recognition. This is useful for recognition keywords (or standard identifiers) in such a language as Fortran 🌈
• -no-definitions — no generation of macros (or enumeration) defining identifiers of keywords 🚫
• -interface — generation of an additional interface file (with suffix .h) 📄
• -export — SHILKA generates macros defining identifiers of keywords in the interface file (instead of in the implementation file). This option has sense only when -interface is present 👑
• -enum — output of an enumeration instead of macro definitions for identifiers of keywords 🔢
• -pprefix — usage of a prefix instead of KR_' (default) for names of generated objects 🏷️
• -time — output of time statistics of the SHILKA run into stderr ⏱️
• -fast n — if the number of rested unchecked characters is less or equal to n, then the functions strcmp or strncmp is not used at all. Instead of this, simply comparing rested unchecked characters is used. This can speed up keyword recognition. The default value of the parameter is 3 ⚡
• -w — disable generation of all warnings 🔇
• -h, -help — output of a brief help message about SHILKA usage 🙋‍♀️
• -v — creation of a description file containing details how the code generated by SHILKA will recognize the keywords 📝

---

🎀 FILES 🎀

• file.shilka — SHILKA specification file
• file.c — generated C implementation file
• file.cpp — generated C++ implementation file
• file.h — generated interface file

There are no any temporary files used by SHILKA — zero, none, nada 💀

---

🦋 ENVIRONMENT 🦋

There are no environment variables which affect SHILKA behavior. literally none, bestie 🧚

---

🔥 DIAGNOSTICS 🔥

SHILKA diagnostics is self-explanatory. iykyk 💅

---

👑 AUTHOR 👑

Vladimir N. Makarov, vmakarov@users.sourceforge.net 💖

---

🌈 SEE ALSO 🌈

msta(1), oka(1), sprut(1), nona(1). SHILKA manual. 🫶

---

💀 BUGS 💀

Please, report bugs to cocom-bugs@lists.sourceforge.net 😭

---

okay bye bestie — this page is from COCOM, dated 5 APR 2001, and it's the SHILKA(1) manual 💖🫶✨