<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Hi Ralph --<div><br></div><div>Now I can see the issue. Thanks for reporting. Feel free to fix the issue and put it into the inbox: <a href="https://squeak.org/development_process/" style="font-size: 10pt"><span style="font-size: 10pt">https://squeak.org/development_process/</span></a></div><div><br></div><div>You may also attach a simple change-set to a post here on the list.</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 23.02.2023 05:05:01 schrieb Ralph Boland <rpboland@gmail.com>:</p><div style='font-family:Arial,Helvetica,sans-serif'>#findFeatures at least works correctly. That is it does not add an<br>unintended leading space<br>for the String 'AnExampleString' like #fromCamelCase does when the<br>first letter is capitalized.<br><br>I think I will just fix this bug privately. If anybody wants my code<br>just email me.<br><br>Thanks all for your time.<br>Ralph<br><br><br>> Hi Ralph --<br>><br>> This is Etoys-only protocol. It hasn't changed substantially since at least 2007. What do you<br>> think the correct behavior should be for #fromCamelCase? An extra empty string in the set?<br><br>> Please use #findFeatures instead --- even though it has the same answer for<br>> 'AnExampleString', > which you apparently do not agree with. :-)<br>><br>> Best,<br>> Marcel<br><br><br>> > Am 22.02.2023 08:46:16 schrieb Ralph Boland <rpboland@gmail.com>:<br>> > I have found a simple bug in Squeak 6 (and 5.3)<br><br>> > 'anExampleString' fromCamelCase returns: 'an example string' .<br>> > But<br>> > 'AnExampleString' fromCamelCase returns: ' an example string' .<br>> > I assume the latter is wrong.<br><br>> > How do I report this bug?<br>> > Should I fix this bug and add the fix to the bug report<br>> > or leave it for someone else to fix?<br><br>> > My guess is I will need to fix this bug anyway because I will likely<br>> > need it fixed before a fix can be released.<br><br>> > Ralph Boland<br><br></rpboland@gmail.com></div></blockquote>
</div></body>