"Replace all" in type defined clusters

[wiebe@CARYA]

---

@_Y_ wrote:

---

wiebe@CARYA wrote:

There must be some complication that distinguishes a "test project" from a "real large project". I don't think it's just scale.

I had problems with type defs owned by classes, where the class was blocked because the type def was changed, and the type def was blocked because the class was changed. I tend to forget the details once I found a workaround. But a seemingly simple "recursion" like that could be the showstopper.

---

Yes, this is the problem. I cannot find the basic difference between "test" and "real" projects.

Yes, typedefs can belong to GOOP classes or LVLIB-s. However replacement works with "test".

Recursion? May be. What happens if a typedef is member of a class while the class attributes contain this typedef? I shall test it.

---

Recursion is a misnomer (my bad), it's more of a cyclic dependency situation.