&gt; I presume @eht16 ensures no C library problems when bundles are made, but anyone building it themselves may have an issue.<br>
<br>
Yes. The binaries and bundles provided by us should be fine as<br>
they(Geany, GLib, GTK, Scintilla) all built the same way and all uses<br>
the same C runtime provided by MSYS2.<br>
I&#39;m pretty sure no code in Geany uses mscvrt at all when Geany is built<br>
as documented.<br>
<br>
Of course, if anyone builds Geany with MSVC or manages to compile with<br>
gcc but link against mscvrt or something, then strange things will happen.<br>
I&#39;d consider this as just not supported.<br>
<br>
&gt; @eht16, Why was the `g_` version used in the first place since there is no matching `g_fwrite()`?<br>
<br>
I&#39;m afraid there was no deeper thinking about this but rather &quot;hey,<br>
there is a g_ function for fopen(), so let&#39;s use this because it&#39;s<br>
probably better than the plain one as GLib does stuff for us&quot;.<br>
Today, I&#39;d be rather not that naive but ten years ago, I was.<br>
<br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/1271#issuecomment-256120529">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ5QqDwLxQNHWUezSzWoRJNFC3-PQks5q3kgdgaJpZM4KdtAF">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ2gW617K-YySPov26LPGH4mj_Ul3ks5q3kgdgaJpZM4KdtAF.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/issues/1271#issuecomment-256120529"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@eht16 in #1271: \u003e I presume @eht16 ensures no C library problems when bundles are made, but anyone building it themselves may have an issue.\n\nYes. The binaries and bundles provided by us should be fine as\nthey(Geany, GLib, GTK, Scintilla) all built the same way and all uses\nthe same C runtime provided by MSYS2.\nI'm pretty sure no code in Geany uses mscvrt at all when Geany is built\nas documented.\n\nOf course, if anyone builds Geany with MSVC or manages to compile with\ngcc but link against mscvrt or something, then strange things will happen.\nI'd consider this as just not supported.\n\n\u003e @eht16, Why was the `g_` version used in the first place since there is no matching `g_fwrite()`?\n\nI'm afraid there was no deeper thinking about this but rather \"hey,\nthere is a g_ function for fopen(), so let's use this because it's\nprobably better than the plain one as GLib does stuff for us\".\nToday, I'd be rather not that naive but ten years ago, I was.\n\n"}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1271#issuecomment-256120529"}}}</script>