Re: [vos-d] eliminating flex/bison

grammar that made it unsafe. It was really too easy for me to just chuck the whole thing and replace it with boost::regex. I can certainly send you the grammar if you're interested. -- Braden McDaniel e-mail: <[EMAIL PROTECTED]> <http:/

Re: [vos-d] eliminating flex/bison

On Wed, 2005-06-22 at 23:51 -0400, Braden McDaniel wrote: > On Wed, 2005-06-22 at 23:12 -0400, Peter Amstutz wrote: > > > Braden, you're using spirit for OpenVRML, right? > > Used to. I made a URI parser with it. > > > What's your experience been? >

[vos-d] Re: struggling with Windows...

Hugh Perkins wrote: msvcrt.dll is the old pre-.net dll, msvcr71.dll is the .net dll The import libraries have teh same name in each case (msvcrt.lib, msvcprt.lib) but point towards a differently named dll, one of those above, depending on the compiler version. This, from

Re: [vos-d] Re: struggling with Windows...

res wrote: On 16.08.2005 22:24, Braden McDaniel wrote: Well that's annoying. So why bother with msvcr71.dll at all? Why not just build with /MT instead and pull in the static library? What does using the DLL runtime buy you? Disk and RAM space savings if you have multiple modules.

Re: [vos-d] Re: struggling with Windows...

On Tue, 2005-08-16 at 22:11 -0400, Peter Amstutz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tue, 16 Aug 2005, Braden McDaniel wrote: > > >> One heap - you can free memory allocated in some other module. > > > > That's the major selli

Re: [vos-d] migrate to subversion?

r/boo/file--no way. You'll have to remember where it was when it you deleted it. svn is remarkably little help with things like this. Using the directory structure to model branching was simply the Wrong Answer. And I fear svn has gone to far down that road to turn back. -- Braden McDanie

Re: [vos-d] migrate to subversion?

On Thu, 2005-12-01 at 16:41 -0500, Peter Amstutz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Wed, 30 Nov 2005, Braden McDaniel wrote: > > > Suppose you have a file foo/bar/file. foo/bar/file gets deleted. The > > foo/bar branch becomes foo/baz.

Re: [vos-d] VOS 0.23.0-pre2 released

for wxThread > typeinfo for wxTimer > typeinfo for wxListBase > typeinfo for wxFrame > typeinfo for wxControl > typeinfo for wxPanel > typeinfo for wxGauge > collect2: ld returned 1 exit status I'm betting that in both of these cases, wx was built with RTTI disabled. If

Re: [vos-d] VOS requirements

t geometry file formats. So the same semantic data could be meaningful regardless of whether the geometry was expressed in X3D, COLLADA, or whatever. Anyone who's ever used HTML and CSS should be seeing an analogy here. Whether the semantic metadata lives out-of-ban

Re: [vos-d] VOS requirements

On Fri, 2007-01-26 at 11:51 +0100, Karsten Otto wrote: > Am 26.01.2007 um 01:39 schrieb Braden McDaniel: > > > [...] > > Why isn't this a job for a metadata spec? It seems to me that this > > kind > > of semantic information is too application-specific to enco

Re: [vos-d] Message handler problem

given > that there's enough information to recognize that it's virutal inheritance > at compile-time? Because recognizing that virtual inheritance is involved is the extent of what can happen at compile time. Introducing virtual inheritance means that the class layout cannot be re

Re: [vos-d] Choosing a GUI toolkit for S5

Also, GTK+ can interact with OpenGL via GtkGLExt. Also, with regard to the language issue, Gtkmm is worth pointing out. Gtkmm is a very high quality modern C++-aware C++ wrapper for GTK+. -- Braden McDaniel e-mail: <[EMAIL PROTECTED]> <http://en