As I will likely have to secure some external FTP sessions soon and the endpoints the current FTP connects to are vague in what they support:
Here is the difference:
SFTP (SSH file transfer protocol) is a protocol that provides file transfer and manipulation capabilities. It can work over any reliable data stream, but is typically used with SSH
“FTP over SSH” uses the regular old FTP protocol, but an SSH tunnel is placed between client and server.
Check out $(BDS)\source\cpprtl\Source\misc\unmangle.c – it contains the source code for the unmangling mechanism used by TDUMP, the debugger and the linker. (C++Builder and Delphi use the same mangling scheme.)
…
This has been around as long as BCC itself. However the file was called um.c instead of unmangle.c in older versions
A while ago, I heard about xmllint, a program that can parse and query xml from the command-line.
Later, I discovered it can also parse html, can recover from xml/html errors and has an interactive shell that has a lot of commands (see table below) to navigate through the loaded command.
The relevant command-line options:
--recover
--html
--shell
Note that --recover will output failing input to stderr. You can ignore that using 2> /dev/null
Fantasque Sans Mono: A programming font, designed with functionality in mind, and with some wibbly-wobbly handwriting-like fuzziness that makes it unassumingly cool. Development hosted on Github: [Wayback] https://github.com/belluzj/fantasque-sans OFL (SIL Open Font License). Category: Monospaced
Interesting, as I thought Mac OS X Yosemite and up – having Python installed – would also keep Python up-to-date, but they don’t.
Hence:
Installing Python on Mac OS X
The latest version of Mac OS X, Yosemite, comes with Python 2.7 out of the box.
…
The version of Python that ships with OS X is great for learning but it’s not good for development. The version shipped with OS X may be out of date from the official current Python release, which is considered the stable production version.
Update: Reduced CPU usage on server when using a large number of time triggers.
Update: Reduced wait time between time triggers running simultaneously.
Update: Reduced CPU usage and throughput of stage queue.
Update: The >> operator is now implemented in repository rules. This is used to clean the destination folder before copying files. It is useful when a stage can run on the same agent as a previous stage as the agent workspace is not automatically cleared between stages. Note: We have also changed the default workspace and repository rules so that the >> operator is used for any server to agent rules in new stages. This is to ensure that the workspace is always cleared and are no surprises dependent on the agent the stage runs on. This can be changed to a single > to use the previous behaviour.
Update: Environment variables now expanded in all path type property collectors. This will for example allow you to use %HOME% to define the path to check when using a Path Access PlugIn property collector.
Update: Added descriptions and help information to property collector dialog fields.
Update: Queued stages are now prevented from starting in the few seconds after an agent has gone offline.
Fix: Issue where changes to user group membership were not picked up for several minutes unless the service was restarted.
Fix: Triggers were not being monitored after a disabled configuration was re-enabled.
Fix: Issue where agents with unlimited concurrent stages would not be selected to run stage.
Nullable<T> = record
… property Value: T read FValue; default;
… end;
Using the default directive to “hoist” the operators of “T“. Currently the default directive only works for array properties by “hoisting” the ‘[]‘ operator. Marking a non-array property with default will make the containing type behave as that type.
This, coupled with some intrinsic compiler knowledge of the Nullable<T> type will make Nullable<T> work without any addition of keywords or other standard functions or procedures.
Using the “default” directive on a non-array property will work for any type, except for having the null-propagation semantics.
When considering language features, I try and not only make it work for the intended purpose, but also broaden reach of any supporting feature. In the above scenario, even user-defined operators on “T” will be properly hoisted and used.
The Wiert Corner - irregular stream of stuff 