Path(3U)

πŸ’– Path(3U) πŸ’–

okay so this is a page from the InterViews Reference Manual and we're talking about Path, bestie. strap in, it's giving ✨dataflow✨


πŸ¦‹ NAME πŸ¦‹

Path β€” the record of connectors visited during dataflow. that's it, that's the whole vibe πŸŽ€


🌸 SYNOPSIS 🌸

#include <Unidraw/path.h>

✨ DESCRIPTION ✨

so a Path object lowkey keeps a lil scrapbook πŸ“– of every connector that's been visited during dataflow. and the transfer functions, state variables, connectors, and basically any other component can peek at what's in that path to figure out whether data should actually be transmitted β€” for example, to avoid circular flow πŸ‘€ which, yeah, you do NOT want that. periodt.


πŸ‘‘ PUBLIC OPERATIONS πŸ‘‘

  • Path(Path* = nil) β€” spin up a brand new path πŸ’« and if you want, you can hand it a Path* and it'll make a duplicate of all the info chillin' in that path. no argument? nil? cool, you get a fresh empty one, we love a blank slate 🫢
  • virtual void Visit(Connector*) β€” mark a connector as having been visited. like checking it off the list, bestie βœ…
  • virtual boolean Visited(Connector*) β€” asks the path: has this connector been registered before? returns whether or not it's already on the list. it's giving detective energy πŸ”

🌈 SEE ALSO 🌈

Connector(3U), StateVar(3U), TransferFunct(3U) β€” go read those too, they're all in the same friend group fr fr πŸ’…


mwah πŸ’œ this page came to you from the Unidraw girlies, dated 6 August 1990, and it's Path(3U) all day every day. no cap. βœ¨πŸ¦‹πŸŒΈ