ADDBDDCIRCUITABL(3)

📦 version 5.1.1-unstable-2025-02, in nixos 26.05, nixpkgs unstable

💅 NAME 💅

okay so bestie, <rainbow>addbddcircuitabl</rainbow> — it converts an abl expression to a bdd node. that's literally it. that's the whole job. ✨

this one lives in section 3 of the manual (the <purple>BDD FUNCTIONS</purple> corner of the world, iykyk), so like… yeah. library call. 🎀

🌸 ORIGIN 🌸

fr fr this software belongs to the <hotpink>ALLIANCE CAD SYSTEM</hotpink>, developed by the ASIM team at LIP6 laboratory of Université Pierre et Marie CURIE, in Paris, France. iconic, honestly. 👑

like, they're on the web AND they have email. main character energy. 💌

✨ SYNOPSIS ✨

#include "bdd101.h"
bddnode ∗addbddcircuitabl( BddCircuit, Expr )
  bddcircuit ∗BddCircuit;
  chain_list ∗Expr;

that's the whole vibe right there 🫶

🦋 PARAMETERS 🦋

  • BddCircuit — the bdd circuit. yes. that one. the circuit. 🧚
  • Expr — the expression to convert. the one we're translating. no cap.

💖 DESCRIPTION 💖

okay so <pink>addbddcircuitabl</pink> converts the abl expression Expr to a bdd node. simple. slay.

the BddCircuit is what's used to translate the atomic expressions into variable nodes — it's giving translator energy. 🌈

if a null pointer is given for it, then the default bdd circuit is used. convenient! 💅

and here's the lil plot twist 👀 — if an atomic expression doesn't appear in the BddCircuit input names hash table or output names hash table, then addbddcircuitabl adds a new input by calling the function addbddcircuitin with the BDD_IN_MODE_LAST mode. it just… makes room for it. assertive. we love to see it. 🔥

⭐ RETURN VALUE ⭐

addbddcircuitabl returns a pointer to the bdd node translated. that's your output, bestie. take it. 🎁

💀 ERRORS 💀

  • "bad operator xxx error !" — this means the Expr parameter must be a well defined abl expression. so like… if you get this, check your expression. it's not well defined. it's giving undefined behaviour vibes and not in a cute way 🙈

👑 EXAMPLE 👑

here's the full little demo, copied exactly because obviously:

#include "bdd101.h"
   bddsystem  ∗BddSystem;
   bddcircuit ∗BddCircuit;
   bddnode    ∗BddNode;
   chain_list ∗Expr;
   BddSystem  = createbddsystem( 100, 1000, 100, 50000 );
   BddCircuit = createbddcircuit( "hello_world", 10, 10, BddSystem );
   Expr = createablbinexpr( ABL_AND,
                            createablatom( "i0" ),
                            createablatom( "i1" ) );
   BddNode = addbddcircuitabl( BddCircuit, Expr );
   freeablexpr( Expr );
   Expr = convertbddcircuitabl( BddCircuit, BddNode );
   /* displays (i0 and i1) */
   viewablexpr( Expr, ABL_VIEW_VHDL );
   freeablexpr( Expr );
   destroybddsystem( (bddsystem ∗)0 );
   destroybddcircuit( (bddcircuit ∗)0 );

and yes, that /* displays (i0 and i1) */ comment is doing the lord's work. it really does display (i0 and i1). ate. 🍓

🧚 SEE ALSO 🧚

go read those too, bestie. iykyk. 🦋

🔥 BUG REPORT 🔥

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

we need your feedback to improve documentation and tools. like genuinely — send the feedback. they're asking. be the main character who files the report. 💌

ngl the sweetest part: this whole page is brought to you by <purple>ASIM/LIP6</purple>, dated <pink>October 1, 1997</pink> — yes, 1997, she's vintage and she still slays. periodt. 💅✨
📦 where this page comes from