9 ms·

Well... more like this stuff: http://git.dev.opencascade.org/gitweb/?p=occt.git;a=tree;f=tests/bugs;h=91f464799202d78722c76dd032898d210e23ca1f;hb=HEAD http://g

by kanzure 12y ago

Well... more like this stuff: http://git.dev.opencascade.org/gitweb/?p=occt.git;a=tree;f=tests/bugs;h=91f464799202d78722c76dd032898d210e23ca1f;hb=HEAD http://git.dev.opencascade.org/gitweb/?p=occt.git;a=tree;f=t... And then all the other not included tests.... Btw, the OCE team has done some great work, especially considering what their task is and what they have to work with. If you must use OpenCASCADE, then use OCE.

desdiv 12y ago
Sorry, I'm still not following you. OpenCASCADE is the upstream; OCE is the downstream. OpenCASCADE is LGPL 2.1 and OCE is LGPL 2.1, so that means OCE can pull every single line of code from OpenCASCADE. Are you saying OCE is not pulling certain tests downstream despite being free to do so? Or are you saying that some OpenCASCADE test are still close sourced? If so, then what would be the motivation behind keeping these tests close sourced?
- kanzure 12y ago
  > Or are you saying that some OpenCASCADE test are still close sourced? Yes, that's the one I mean. There's even lots of references on the public parts of their bug tracker to these tests. > what would be the motivation behind keeping these tests close sourced? There are so many that I can't even begin to speculate which ones might be the case here... maybe they lost them, maybe they have Top Secret commercial data (like BRL-CAD's other test suite, which contains military data), maybe they don't want anyone to do major refactors without putting in the effort to make new tests..... Like I said, lots of possible reasons. I haven't asked them.