Muttering into the void.
Developing in Visual C++, I came across the dreaded “Application failed to initialize properly” error. This is usually caused by a missing DLL, but in this case all the DLLs were there.
I finally realized that a static variable in one of the DLLs was throwing an exception in its constructor, causing the load to fail.
I ran into the strangest problem today. After upgrading to IE8, my Visual Studio 2005 (this is for work on a legacy system) debugger would detach all by itself soon I hit F5 to debug an ASP.NET page via IIS.
Turns out this is due to IE8’s use of separate processes for tabs. To disable this behavior, set a DWORD value of 0 in the key HKLM\Software\Microsoft\Internet Explorer\Main\TabProcGrowth.
Of course this negates the benefit of running tabs in separate processes, but the debugger will not automatically detach.
Update: make sure you set the registry value in the 32-bit hive.
So I’m trying to build NeuroLab on OS X. It builds and links, and I’ve written a script to munge the libraries’ names.
It crashed on start, due to a different order of static member initialization in libraries than on either Win32 or Linux. Fixed that.
Now it just randomly crashes deep in the Qt library, while drawing text. I can’t figure out how to point gdb to the Qt sources.
I have released a new version of IronMeta. It makes the syntax closer to the usual OMeta syntax.
I also fixed a bug that caused some redundant evaluation to be done. Performance is still pretty bad, though.
I will be focusing on
You can download the new version at SourceForge, or via Subversion at https://ironmeta.svn.sourceforge.net/svnroot/ironmeta/tags/1.2/.
IronMeta provides a programming language and application for generating pattern matchers on arbitrary streams of objects. It is an implementation of Alessandro Warth’s OMeta system for C# on .NET.