auxinit(3)

πŸ“¦
version 1.1.2 Β· 3 versions
, in fedora 43

πŸ’– auxinit(3) β€” Library Initialization πŸ’–

okay bestie, welcome to auxinit, your little backstage-pass page in the MEPACK manual (section 3, library functions, we love a section 3 moment). Short version: this is where you learn how to Initialize the MEPACK library. That's it. That's the whole job. But it's a very important job, so let's get into it 🫢


✨ SYNOPSIS ✨

🌸 Functions

  • void mepack_init (void) β€” Initialize MEPACK from C.
  • subroutine mepack_initialize () β€” Initialize MEPACK from Fortran.

🌈 Detailed Description

So like, you have to initialize the MEPACK library. Not optional, not "eh I'll do it later" β€” necessary. Here's why, fr fr:

  • MEPACK uses some static internal parameters, and
  • it also relies on the setting of some environment variables.

Because of all that, it is necessary to initialize MEPACK first. So this section contains the required functions. No init, no vibes. It's giving "read the instructions before you touch anything" πŸ’…


πŸ‘‘ Function Documentation

πŸŽ€ void mepack_init (void )

Initialize MEPACK from C, bestie. The mepack_init function is a wrapper around the mepack_initialize routine, so it's easy to call from C. Convenience icon behaviour, honestly.

Now here's the tea on calling it more than once β˜•:

  • If you accidentally call both the C and the Fortran initialization routine, only the one which is called first is executed.
  • If the function is called twice, nothing happens.

No drama, no double-init chaos, the library is just chill like that ✨

See also

  • mepack_initialize
Definition at line 34 of file init.c. πŸ“

πŸ¦‹ subroutine mepack_initialize

Initialize MEPACK from Fortran. The MEPACK_INITIALIZE subroutine initializes MEPACK if it is called from Fortran. It's the main character of this whole page, ngl.

What does it actually do, you ask? So glad you asked, bestie:

  • it initializes the machine specific parameters, and
  • it reads the environment variables.

And then, the tuning file situation πŸŽ€:

  • If a user defined tuning file is provided, that file is loaded.
  • Otherwise, the builtin tuning file is loaded.

Custom file or default file, either way you're getting tuned. Slay.

See also

  • mepack_init
Definition at line 27 of file init.f90. πŸ“

🧚 Author

Generated automatically by Doxygen for MEPACK from the source code. (Not a human author, just a robot doing its little documentation dance πŸ€–πŸ’«)


πŸ“ SEE ALSO

  • mepack_initialize
  • mepack_init

(Yes, they're each other's see-also. Mutuals. We respect it.)


MEPACK Β· Version 1.1.2 Β· Thu Oct 9 2025 00:00:00 Β· auxinit(3)

and that's the whole page, bestie!! go init your library, you absolute icon, and remember: call it first, call it once, and let it cook πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«Ά

πŸ“¦ where this page comes from