Many Bazel attributes support the use of predefined variables
and functions such as @D for output directory or
$(location //foo:bar) to get the path to a label. But what
if you want to apply some sort of tranformation to these
variables, or define your own custom make variables? This
blog post explains how.
Let’s say you are using Bazel to build a C program which links against
a system-provided version of libcurl, the multiprotocol file transfer
library. What is the best way to link your program against this library
within Bazel? This blog post provides an answer to that question.
In the Windows XP login screen, the password text box will warn you with a balloon tooltip if you accidentally turn Caps Lock on. The balloon tooltip appears to be a Windows tooltip common control with the TTS_BALLOON style.
To replicate this functionality, I decided to write a function called ShowMsgBalloon() which, given a control and the various balloon tooltip parameters, creates and shows the balloon tooltip below the control.
Read more...
Windows C++ developers remain all too familiar with the standard Windows crash dialog. This post is an attempt to teach developers how to understand the data the crash dialog reports to diagnose difficult issues. A basic understanding of assembly language is assumed; for more background on these topics please read Matt Pietrek’s “Under The Hood” articles in the Microsoft Systems Journal February 1998 and June 1998 issues.
To begin with, let’s write an application that crashes with a null pointer dereference:
Read more...
Avoid atoi() and related functions: they do not distinguish between invalid input and a valid “0″ string. Use functions which properly report errors, such as strtod().
On some Windows operating systems (primarily Windows 95, 98, and ME), GetOpenFileName() and GetSaveFileName() (and wrappers of these functions such as MFC’s CFileDialog) will permanently change the process’s current working directory unless the OFN_NOCHANGEDIR option is specified. As you can imagine, this can easily break your application if you ever rely on the current working directory being set to a particular value (such as if you open files using relative paths).
Read more...
Consider the following piece of code (adapted from a real-world bug):
1 2 3 4 5 6 7 BOOL IsDirectory(LPCTSTR strPathName) { DWORD dwAtts = GetFileAttributes(strPathName); if (dwAtts == INVALID_FILE_ATTRIBUTES) return FALSE; return (dwAtts == FILE_ATTRIBUTE_DIRECTORY); } This function will work most of the time, but every now and again it will run across a directory which it will claim isn’t one. Why?
The problem is caused because dwAtts is a bitfield (see the GetFileAttributes() documentation).
Read more...
At work I recently was given the task to support gzip-based HTTP response compression in a C++ MFC application. For a while I was convinced that there was no way to support in-memory decompression of gzip-compressed data using zlib, and so I wrote the gzipped data to a temporary file and then used the gzopen()/gzread()-family of functions in zlib to read it back (as described in the zlib manual).
I spent a lot of time looking at the zlib code to try to see why the in-memory streaming decompression function inflate() wasn’t working for gzip-compressed data and determined that zlib wasn’t recognizing the gzip headers.
Read more...
