<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Jakob.<div><br></div><div>Or did you mean a fall-back in the FFI-Kernel package? Well, you can always disable styling.</div><div><br></div><div>Well, if you cannot save/compile the source anyway, it makes no sense to implement a fallback in Shout for arbitrary stuff in a pragma.</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 15.06.2020 09:35:18 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Jakob.<div><br></div><div>> <span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Could we have a fallback implementation</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Hmm... not a robust one. The current fallback is to parse the standard keyword pattern: <foo: 42 bar: 'huh' baz: #hmm></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">As soon as a custom pragma parser comes into play --- like the one for FFI calls --- you can only "fail" as a Shout parser if you come across an unexpected token.</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Well, when parsing pragmas, we could implement a different kind of #fail. We could look for the next > and try to finish parsing the pragma. This would only work if there is no other > in the middle ... #> and '>' are fine, I suppose.</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Best,</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Marcel</span></div><div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 14.06.2020 23:46:48 schrieb Jakob Reschke <forums.jakob@resfarm.de>:</p><div style="font-family:Arial,Helvetica,sans-serif">
<div dir="ltr">Hi Marcel,<div><br></div><div>Could we have a fallback implementation in Tools that just ignores/does not highlight the contents of any <...> at the top of the method?</div><div><br></div><div>And if you load the appropriate tools package for your feature (FFI), then you get better styling for the constructs it supplies.</div><div><br></div><div>Kind regards,<br>Jakob</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am So., 14. Juni 2020 um 08:29 Uhr schrieb Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de">marcel.taeumel@hpi.de</a>>:<br></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex;border-left: 1px solid rgb(204,204,204);padding-left: 1ex;min-width: 500px"><div id="gmail-m_-91201151110266133__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: rgb(0,0,0)">Hi all!<div></div><div><br></div><div>I just extracted FFI-specific code for pragma styling into the FFI-Tools package.</div><div><br></div><div>I am not sure whether this is good, because now you *have to* load that FFI-Tools package to browse method sources with FFI pragmas having Shout enabled. So, that's a change. All my other additions to FFI-Tools have been new so far.</div><div><br></div><div>Having FFI-Pools and FFI-Kernel only lets you compile this method:</div><div><img id="gmail-m_-91201151110266133f46502d5-149d-4865-a063-b8bfbac49cb4" src="cid:172b4cadf35cb971f161" width="auto"></img><br></div><div><br></div><div>After installing FFI-Tools, you get this experience:</div><div><img id="gmail-m_-91201151110266133ba001aa6-2804-418b-b281-68fd83d34875" src="cid:172b4cadf35cb971f162" width="auto"></img><br></div><div><br></div><div>Here is another take on package organization for the Squeak FFI project:</div><div><a href="http://forum.world.st/FFI-FFI-Pools-mt-19-mcz-tp5117611p5117643.html" target="_blank"><span style="font-size: 10pt">http://forum.world.st/FFI-FFI-Pools-mt-19-mcz-tp5117611p5117643.html</span></a><br></div><div><br></div><div>Please share your thoughts on this matter :-)</div><div><br></div><div>Best,</div><div>Marcel</div></div><br>
</blockquote></div>
</div></blockquote></div></div></blockquote>
</div></body>