[Cuis-dev] Possible normalization of code files to use ANSI assignment. Re: New handling of assignment and return arrows

[Juan Vuletich]

Hi Folks,

Before I push this to GitHub, a couple of notes:

- The only preference to control this would be called 
#showAssignmentAsLeftArrow , and will control both assignments and returns.

- The default value would be true.

Anyone having concerns with this, please comment, so we can find the 
best solution.

Thanks!

On 3/9/2023 6:18 PM, Juan Vuletich via Cuis-dev wrote:
> Hi Folks,
>
> This is finally here.
>
> With the attach, files and clipboard will always use '^' and ':='. 
> When entering code, you can use '_' or ':=', and '^' as usual.
>
> What you see in the display is controlled by a single preference that 
> affects all code (the one you are typing and all the code in the 
> system). Options are:
> - All assignments and returns are ANSI: ':=' and '^'. This is, you see 
> what is stored in code files.
> - All assignments and returns are in Smalltalk-80 style: LeftArrow and 
> UpArrow.
>
> There's no need to convert existing files. Code files including '_' 
> for assignment are still valid for reading.
>
> Please try the attach, and give feedback. If we reach consensus, I'll 
> push it to GitHub.
>
> Thanks,
>
> On 10/21/2022 1:16 PM, Juan Vuletich via Cuis-dev wrote:
>> On 10/21/2022 12:52 PM, Gerald Klix via Cuis-dev wrote:
>>> On 21.10.22 16:40, Juan Vuletich via Cuis-dev wrote:
>>>>>
>>>>
>>>> A possible next step is to always save files using the ANSI 
>>>> assignment syntax: ':=', and make the conversion a preference. This 
>>>> would mean that you'll no longer be able to chose between 
>>>> colon-equal and left arrow when writing your code. Files would 
>>>> always be ANSI, and the preference would control just how you see 
>>>> all of them.
>>> This will make code generation much simpler.
>>>>
>>>> Pros include better interoperability.
>>>> Cons include a bit less control over your own code.
>>> One thing is not clear to me:
>>> Will I be still allowed to type “_” and it will be replaced
>>> by “:=” in the code, whereas some other character, preferably
>>> an arrow “←” or depending on preferences some other
>>> string like “⬅” or ”:=” will displayed?
>>> IHMO, this would be the ideal behavior.
>>
>> Exactly. That's my proposal.
>>
>>> HTH,
>>>
>>> Gerald
>>
>> Thanks,
>>
>
>


-- 
Juan Vuletich
cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
linkedin.com/in/juan-vuletich-75611b3
twitter.com/JuanVuletich