# Learning about SPARK dependency contracts

**URL:** <https://forum.ada-lang.io/t/learning-about-spark-dependency-contracts/1033>\
**Category:** General\
**Tags:** spark\
**Created:** [July 29, 2024, 6:27pm UTC](https://forum.ada-lang.io/t/learning-about-spark-dependency-contracts/1033 "2024-07-29T18:27:41Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![mgrojo](https://forum.ada-lang.io/user_avatar/forum.ada-lang.io/mgrojo/32/15_2.png) [@mgrojo](https://forum.ada-lang.io/u/mgrojo)\
**Post date:** [August 10, 2024, 7:54pm UTC](https://forum.ada-lang.io/t/learning-about-spark-dependency-contracts/1033/4 "2024-08-10T19:54:58Z")

</div>

By the way, with the `--flow-debug` switch [1] I get the same output (besides the error) when the exit is present and when not, so it doesn’t give a clue about why it is coming to that conclusion.

[1] See output in [How does `gnatprove --flow-debug` use graphviz?](https://forum.ada-lang.io/t/how-does-gnatprove-flow-debug-use-graphviz/1067/1)

---

_[View the full topic](https://forum.ada-lang.io/t/learning-about-spark-dependency-contracts/1033)._