Stringly Typed Booleans

I’m getting rather hacked off seeing boolean properties typed as strings. Stringly typed is a phrase I learnt off a post from the excellent Coding Horror blog and it describes a phenomena whereby properties that are of a specific type, e.g. Boolean, Date, int, are stored needlessly as strings.

I’m working on a website that communicates with a money laundering service to check whether an individual is “bad” or not. Individuals can pass the test, but importantly it is possible to pass the test with some warning flags raised. If any of the warning flags are raised then an email should be sent off to compliance for them to do…whatever it is they do. Fair enough right?

The warning flags are obviously booleans. There was either a warning raised or there wasn’t – there are no two ways about it (no pun intended). In the serialized response, the warning flags are encoded as “Yes” or “No”…which is understandable. Now, upon receiving the response, it is parsed and turned into an internal representation. This is where things get really weird. The programmer that coded the object that stores the response from the service has decided to encode the warnings as strings, initialised to “”. Which is totally fucking bonkers.

Why?

Well, now our boolean warnings aren’t really booleans – they have WAY more than two possible values and the meaning of these values is subjective. One may consider “”, null, “No” as false, but could conceivably also consider “false” or “0″. We get the same sort of problem with true – “Yes”, “1″, “true” and then we get a whole load of unknown values which is every other possible string in the world. Which might be considered to be true.

So how the hell can any number of programmers work on this piece of code without introducing errors because of differing definitions of truthy and falsey values? Well, they can’t. To illustrate the problem further, even loosely typed languages differ in their boolean coercion, for example JavaScript and PHP:

<script>
if("0") alert('Opposite day!');
</script>

<?php
if("0") echo 'Opposite day!';
?>

JavaScript considers “0″ true but PHP considers it false. Personally I think JavaScript is “right” here, but as I said before, it is totally subjective.

The icing on the cake is of course the extra code you have to write to check the truthy or falsey string values. Something along the lines of “if x is not null and not empty and not the word No then it is probably true…probably”, which would otherwise have been coded as “if x then true” if x was a boolean – which is orders of magnitude shorter.

Of course, there are some bat shit crazy strongly typed languages that allow you to assign null to a Boolean, but that is a different story altogether.

5,110 thoughts on “Stringly Typed Booleans

  1. 從英超、西甲、德甲到中超,全球各大足球聯盟的足球比分即時比分都在這裡。

  2. Those who want to play Deal or No Deal with bitcoin go through several rounds of the game, so we can proceed with this complaint accordingly. I did think it was a bit disappointing the symbols don’t do anything special, the more chances the player has to win a jackpot. One of your objectives when playing Blackjack is to win, you will get Kickbux points. Reactoonz スロットは、一般的なビデオスロットで見られるスキャッターを揃えてフリースピンを発動させ勝利を呼び込むスタイルとは違い、「切断」「破裂」「破壊」「交換」など多彩なボーナスフィーチャーが取り揃えられているんです。そんな背景から、世界中のプレイヤーから高い評価を受けています。 Reactoonz(リアクトゥーンズ)は、大手カジノプロバイダーとして知られるPlay’n GO(プレインゴー)社の手掛ける、オンラインカジノで大人気のスロット機種のひとつです。
    https://alasan123.com/%ef%bc%88gates-of-olympus%ef%bc%89/
    最近では続編となる「リアクトゥーンズ 2」も登場し人気となっていますが、個人的にはオリジナルのこちらの方がおすすめ。 リアクトゥーンズスロットはカジノによくあるタイプのスロットゲームとは違い、どちらかというと世界的に人気ゲームのぷよぷよに近い(パズルゲーム)タイプのゲームとなっております。ぷよぷよタイプなのにスロットゲーム?と思われる方もいるかもしれませんが、れっきとしたカジのスロットゲームの部類に入るゲームとなっております。 トゥルードラゴンXでは、「R」という図柄が一直線に揃うとリスピン(再抽選)となり、リスピンが3連続続けばボーナスゲームに突入します。ボーナスゲーム中はランダムに倍率が付与され高配当のチャンス。さらに、銀の龍や金の龍を3回揃えることでドラゴンを召喚!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>