DESTROYBDD(3)

🦋 DESTROYBDD(3) — BDD functions 🦋

okay bestie, sit down, hydrate, because we're about to learn how to clean up after ourselves. it's giving responsible queen energy. this one lives in section 3 of the manual (the library functions section, iykyk), and it's literally called DESTROYBDD — no cap, that's the whole title. 💅

---

🌸 ORIGIN 🌸

so this software? it belongs to the ALLIANCE CAD SYSTEM, which was developed by the ASIM team at the LIP6 laboratory of Université Pierre et Marie CURIE, in Paris, France. 🇫🇷✨ iconic institution behavior fr fr.

• Web : http://asim.lip6.fr/recherche/alliance/
• E-mail : alliance-users@asim.lip6.fr

like, they have a website AND an email, they're that girl. 🫶

---

✨ NAME ✨

destroyBdd — removes the BDDs system. that's it, that's the job. she's a closer. 💀

---

🎀 SYNOPSIS 🎀

#include "logmmm.h"
void destroyBdd(level)

short, sweet, devastating. the way she just shows up and ends everything. 👑

---

💖 PARAMETER 💖

• level — desallocate level. (yes bestie, the parameter is literally named after the level of deallocation, we love a self-explanatory name. 🎀)

---

🌈 DESCRIPTION 🌈

so destroyBdd() removes the BDDs system. that's the whole vibe. it's the breakup text of function calls.

but — and this is the important part, do NOT skip this, it's giving spoiler alert — this function can be called only after the initializeBdd() function. so you can't just roll up and destroy something that was never initialized, that's not main character energy, that's chaos energy. 🙈

and here's the tea on level: if level = 0, the nodes are saved, and it's possible to go through the BDD for treatments that don't modify the BDD (simulation, for example). so like, level = 0 is the "look but don't touch" option, the museum exhibit of BDD states. 🖼️✨

no modifying the BDD after level = 0 bestie, it said what it said. non-modifying treatments only. 🔥

---

🍓 EXAMPLE 🍓

here's how the girlies do it, verbatim:

#include "mutnnn.h"      /* mbk utilities */
#include "logmmm.h"

initializeBdd(MEDIUM_BDD);

/* application using BDD ... */

destroyBdd(1);

see how she initialized first, then did her little application thing, then destroyed? that's a full arc. character development. 🌸

---

💜 SEE ALSO 💜

go read these next, bestie, they're all in the family:

• log(1)
• bdd(1)
• initializeBdd(3)
• gcNodeBdd(3)
• markAllBdd(3)
• numberNodeAllBdd(3)
• resetBdd(3)

---

⭐ BUG REPORT ⭐

so this tool is under development at the ASIM department of the LIP6 laboratory. 👀

they need your feedback to improve documentation and tools. so like, if something's weird, tell them! they're literally asking! that's so vulnerable of them, we love that. 💖

---

and that's the whole page babes — brought to you by ASIM/LIP6, dated October 1, 1997 (yes, she's a vintage icon, the manpage equivalent of a Y2K baby tee 💅), filed under DESTROYBDD(3). go forth and deallocate responsibly. 🦋✨🎀