Programming

For years we have scoured the deserts of Iraq for WMD’s to no avail. Then from out of nowhere a WMD is unleashed on American soil. Since 9/11 the government has told us that they had a plan. If we just trust in them and let them spend money to fund this plan, they would keep the WMD’s off our shores. They also said that a WMD being loosed on a major American city was inevitable, so they created the Department of Homeland Security with the mandate of preventing the WMD in the first place and minimizing the damage when it finally happened. As we can now see, they have failed.

Recently, one of the developers that work for me got highly animated while pointing out an issue with the C++ code of another developer on the team. Without all the emotional buildup, it can be summarized as a class is allocated using new with a reference to a containing class passed into the constructor. The constructor adds itself (this) to the collection class and exits. The containers destructor contains all the logic to actually delete the elements it contains. This code works. There are no memory leaks. Some readers may already know. It was all about scope.

Abstract # Background: Traditional compiler architectures, typically built with tightly coupled parsers and code generators, are difficult and expensive to maintain, especially when adapting to frequent changes or multiple variants of a programming language. This is particularly problematic for languages like IEEE-STD-716 ATLAS, which is widely used in test quality assurance and is subject to frequent modifications and customizations across different test stations and equipment.