From furnish at acl.lanl.gov Wed Jun 18 17:04:59 1997 From: furnish at acl.lanl.gov (Geoffrey Furnish) Date: Wed, 18 Jun 1997 09:04:59 -0600 (MDT) Subject: [C++-SIG] Code available! Message-ID: <199706181504.JAA03209@steam.acl.lanl.gov> Hello all, This is just to let you know that Livermore has cut the code we've talked about here previously. You can get "it" via anonymous ftp to: icf.llnl.gov:pub/python/Current_snapshot.tgz "It" is in fact a complete Python source tree. It has basically stock Python 1.4, plus a recent NumPy, plus the Livermore C++ Python binding, plus some of the Livermore graphics stuff (for use with NumPy), and maybe more stuff I can't recall. The current state of the C++ binding has been described in this forum previously. If you've forgotten, you can review the list archival database at python.org. I should add that the relocation from LLNL to LANL caused some interruption in the development of the Python C++ binding, so there is definitely still work that needs doing. If you get the above file, please understand that you are getting a /development snapshot/. The snapshot is produced by a cron job, once a week on Friday nights. There is no representation of quality/stability/etc. It just tars up whatever is in the repository at that time, and puts it up for ftp. True "releases" with some concrete expectation of robustness/quality/etc, are further out. So, just be aware of what you're getting into if you decide to use these snapshots. Paul (LLNL) and I (now LANL) /do/ intend to continue developing this cooperatively. We've had a protracted distraction period as I get resituated here. However, I do have projects on the plate which will involve binding C++ to Python, so I have every intention of continuing with what we have been working on, as will Paul. I will post to this list occasionally as developments are committed into the repository, so that list readers will have some idea of when it is useful to update their snapshots. I also "intend" to write some documentation on the C++ Python binding mechanism we are working on. Finally, I will repeat what I have said several times before, which is that this is a SIG, and it is entirely appropriate for others to describe here what they are doing for binding C++ to Python. We are trying to build a consensus here, so for that to happen, we have to know what people are doing. Cheers to all, -- Geoffrey Furnish email: furnish at lanl.gov LANL CIC-19 POOMA/RadTran phone: 505-665-4529 fax: 505-665-7880 "Here are your ball-peen hammers. Now go malleate some heads!" -Jim Morel _______________ C++-SIG - SIG for Development of a C++ Binding to Python send messages to: c++-sig at python.org administrivia to: c++-sig-request at python.org _______________ From furnish at acl.lanl.gov Wed Jun 18 17:31:45 1997 From: furnish at acl.lanl.gov (Geoffrey Furnish) Date: Wed, 18 Jun 1997 09:31:45 -0600 (MDT) Subject: [C++-SIG] "Acceptable compilers" Message-ID: <199706181531.JAA03304@steam.acl.lanl.gov> BTW, I meant to mention in the prior note, that there are developments on the compiler front. There was discussion on this list previously about issues relating to the availability of "acceptable compilers". At LLNL we defined that as meaning "draft standard conformance, period". And it was mentioned on this list that this was tough for a lot of people to swallow. Well, the size of the pill has decreased quite a bit lately. Kuck and Associates now has released KCC 3.2b (one awesome compiler indeed) on Linux. The price for KCC on Linux is /much/ less than their workstation price. Check their web page at www.kai.com for details, but the base price is $395. Also, there is another compiler on the market based on the same high quality EDG parser, from Commeau computing. That's probably not spelled right, but if you want, I'm sure you can track them down. Anyway, as of only a few weeks ago, they were running a deal where they would ship you a compiler with draft standard language conformance for $50, on just about any Unix platform on the market. The big gotcha with this compiler is they don't have a quality library to go with it. But at least it has a (reputably) solid implementation of exceptions, templates, member templates, defaultable template arguments, RTTI, etc etc etc. Although I do not intend to use this compiler myself, I would be happy to hear from people who try it out on the Python C++ code. Maybe we can work something out for that compiler, if it turns out that a significant fraction of C++ sig users decide to adopt it. -- Geoffrey Furnish email: furnish at lanl.gov LANL CIC-19 POOMA/RadTran phone: 505-665-4529 fax: 505-665-7880 "Here are your ball-peen hammers. Now go malleate some heads!" -Jim Morel _______________ C++-SIG - SIG for Development of a C++ Binding to Python send messages to: c++-sig at python.org administrivia to: c++-sig-request at python.org _______________ From fdrake at weyr.cnri.reston.va.us Wed Jun 18 18:26:55 1997 From: fdrake at weyr.cnri.reston.va.us (Fred L. Drake) Date: Wed, 18 Jun 1997 12:26:55 -0400 Subject: [C++-SIG] "Acceptable compilers" In-Reply-To: <199706181531.JAA03304@steam.acl.lanl.gov> References: <199706181531.JAA03304@steam.acl.lanl.gov> Message-ID: <199706181626.MAA13216@weyr.cnri.reston.va.us> Geoffrey Furnish writes: > Also, there is another compiler on the market based on the same high > quality EDG parser, from Commeau computing. That's probably not > spelled right, but if you want, I'm sure you can track them down. That's almost spelled right! I checked www.edg.com, and fonud a link to www.comeaucomputing.com. The $50 compiler deal appears to still be good from the web page. -Fred -- Fred L. Drake, Jr. fdrake at cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive Reston, VA 20191-5434 _______________ C++-SIG - SIG for Development of a C++ Binding to Python send messages to: c++-sig at python.org administrivia to: c++-sig-request at python.org _______________