On Jul 7, 2011, at 5:30 PM, Mark wrote:
> If we get SCL working, it sounds like a diverse group of organizations will
> be using it. Apparently someone in ECAD uses SCL internally, and there has
> been interest in AP242 as well I believe. I'm personally interested in AP224
> and AP238, and OCE will want APs related to MCAD (203/214/209(?) ) and
> possibly others.
As an express parser, it should certainly parse any and all of the STEP express
AP schemas. In theory, SCL should already parse all of them save for any bugs
and/or changes to express itself that weren't previously exposed. I'll be
curious to see if you get the same AP schema failures using our fork that you
see with the original SCL sources.
> I'm glad to hear that an open-source CAD is getting funding!
Open source since 2004. Continuously funded since 1979. Still a drop in the
bucket compared to the commercial CAD industry, but we have the advantages of
open collaboration, community, and longevity. We can go in any direction and
scratch any itch our community desires.
> These are all things I'd like to see as well. I was even planning on using
> CMake - so you have saved me quite a bit of effort!
The CMake build is relatively new but should already be fully functional. The
entire BRL-CAD build system has been transitioned from autotools to cmake.
Once we get a fuzzy warm feeling that the cmake build is at least as stable as
the autotools build (through a couple release iterations), the autotools build
system files will get yanked.
Since Cmake is all about build system portability, that really begs the
question of dealing with the lexer/parser files in SCL better. As Cliff
mentioned, that is something we're looking into addressing "probably" by
converting the lexer/parser to something not based on flex-bison. We've looked
into several options (including bundling flex/bison for win32), but they are
all riddled with less-than-ideal issues. We could just add generated files to
the repo, for example, but that really makes Windows development of SCL crappy.
None of our devs like working on Windows, but we'd still like to work towards
a solution that doesn't present a collaboration barrier to most (regardless of
their OS).
> I created a mailing list called scl-dev
> (http://groups.google.com/group/scl-dev). Any and all of you are free to sign
> up, whether or not we join forces on SCL.
Sounds great. We can continue SCL-related discussions there.
Cheers!
Sean
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
