BGLAFILE(1)

πŸ“¦ version 4.7a, in arch rolling, fedora 43, fedora 44

πŸ’– BGLAFILE β€” bestie's guide to the Module Access File Generator πŸ’–

okay so. <rainbow>bglafile</rainbow> is a Module Access File generator, and she's from the General Commands Manual section (section 1, obviously). Sit down, grab a strawberry πŸ“, and let me tell you why this tiny little tool is actually so important.


✨ SYNOPSIS ✨

bglafile [ options ] file ...

that's it. that's the whole vibe. options, then a whole pile of files. πŸ’…


🌸 DESCRIPTION 🌸

so <hotpink>bglafile</hotpink> is a Module Access File generator, and what she makes is a file that plays nice with the Bigloo option -afile. πŸ‘‘

A Module Access File is, at its core, a scheme list. Each element of that list is itself a list of at least two elements: a module name, and the file that implements that module.

And here's the part where you have to be careful, bestie, because this one's a mandatory formatting rule 😭:

For BEE (the Bigloo Integrated Development Environment) to be able to retrieve files from module names, it is mandatory that the first parentheses of the global list is left alone on one line.

like, the ( has to be on its own line. do not move it. do not put anything next to it. it needs its personal space, main character energy, and BEE will simply not function if you disrespect it. periodt. πŸ’€


πŸŽ€ OPTIONS πŸŽ€

  • file β€” an file implementing a module. πŸ¦‹ <lavender>bglafile</lavender> reads that file to discover the name of the implemented module. (yes, she reads your file to find out what module you implemented. nosy in a helpful way.)
  • -v β€” Verbose mode. she will talk. πŸ’¬
  • -o <file> β€” Print the Module Access File into file. The default is to print the list on the standard output device. (so if you don't say where, she just yells it into your terminal, which honestly? iconic.)
  • -suffix <suf> β€” Adds suf to the <cyan>bglafile</cyan> source file suffixes list. The default suffixes are "scm", "sch" and "bgl". 🌈

⭐ EXAMPLE ⭐

If the three files exist and contain a legal Bigloo module clause, then:

$ bglafile foo.scm bar.scm gee.scm

could print out a list like:

;; foo
;; Tue Aug  15 12:17:24 1998

(
  (foo "foo.scm")
  (bar "bar.scm")
  (gee "gee.scm")
)

see how the ( is sitting there all by itself on line one of the list? πŸ‘† that's the whole rule from up in DESCRIPTION. she's consistent, we love her for it. 🫢


πŸ”₯ SEE ALSO πŸ”₯

bigloo(1), bgldepend(1), bglmake(1), bglpp(1), bglprof(1), bgltags(1)

(the whole Bigloo friend group. go say hi. πŸ’œ)


πŸ‘‘ AUTHOR πŸ‘‘

Manuel SERRANO, Manuel.Serrano@inria.fr


okay so that's the whole page, bestie, you ate it πŸ’…βœ¨ this was <purple>bglafile</purple> from the General Commands Manual, and the source/version line at the bottom of the original says Aug 15 1998 with BGLAFILE(1) as the footer. so this page is lowkey a 1998 vintage and she still slays. no cap. πŸŽ€πŸ¦‹πŸ’–

πŸ“¦ where this page comes from