<table><tr><td style="">kossebau added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D5621" rel="noreferrer">View Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D5621#108263" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: line-through;" rel="noreferrer">D5621#108263</a>, <a href="https://phabricator.kde.org/p/aaronpuchert/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;" rel="noreferrer">@aaronpuchert</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>By the way, I posted the question to Khronos. <a href="https://www.khronos.org/about/technical-support/" class="remarkup-link" target="_blank" rel="noreferrer">Their preferred channel</a> seems to be opening an issue on one of their GitHub repositories. So I opened issue <a href="https://github.com/KhronosGroup/OpenCL-Registry/issues/27" class="remarkup-link" target="_blank" rel="noreferrer">#27</a> at the <a href="https://github.com/KhronosGroup/OpenCL-Registry" class="remarkup-link" target="_blank" rel="noreferrer">OpenCL Registry</a>.</p></div>
</blockquote>
<p>Good!</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>However, I do not expect an answer. From Khronos' point of view OpenCL source code is just a string in memory. Compiling OpenCL directly from file is not possible. (As far as I know the API.)</p></blockquote>
<p>Mimetype is not just about files in the filesystem, but also in the clipboard, as attachments to messages, network-transferred blobs etc. Kind of type metadata for any byte streams/blobs :) Having that help here and there programs to do better guesses what to do with some blob submitted over a generic API (like clipboard), so it's worth pushing for some type</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>I'm not sure there will ever be a standard type. Not even for C there is: while <tt style="background: #ebebeb; font-size: 13px;">shared-mime-info</tt> defines it as <tt style="background: #ebebeb; font-size: 13px;">text/x-csrc</tt>, I get <tt style="background: #ebebeb; font-size: 13px;">text/x-c</tt> when running <tt style="background: #ebebeb; font-size: 13px;">file -i</tt> on a C source file.</p></blockquote>
<p>Yes, quite frustrating. Was'nt that the nice thing about standards that there are so many to pick from? ;) shared-mime-info tries to encounter that wildness with unregisterd mimetypes a little by here having that alternative also registered, via <tt style="background: #ebebeb; font-size: 13px;"><alias type="text/x-c"/></tt>, so some mapping is possible for code using shared-mime-info (which IIRC <tt style="background: #ebebeb; font-size: 13px;">file</tt> yet has to do, they seem to maintain their own db/magic).<br />
((And then mimetype (usage) is also not the best content type tagging system, e.g. does it have little/no help about format versions (just think about <tt style="background: #ebebeb; font-size: 13px;">application/msword</tt>). But it's what we have right now.))</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R32 KDevelop</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D5621" rel="noreferrer">https://phabricator.kde.org/D5621</a></div></div><br /><div><strong>To: </strong>kossebau, KDevelop, qi437103, aaronpuchert, kfunk<br /><strong>Cc: </strong>nalvarez, kdevelop-devel<br /></div>