[Info-vax] First ship poll: When will the first native x86-64 compilers ship ?

Simon Clubley clubley at remove_me.eisner.decus.org-Earth.UFP
Thu Apr 14 14:08:29 EDT 2022


On 2022-04-14, Dave Froble <davef at tsoft-inc.com> wrote:
> On 4/14/2022 1:17 AM, Richard Maher wrote:
>> On 14/04/2022 12:23 pm, Dave Froble wrote:
>>> On 4/13/2022 10:10 PM, Arne Vajhøj wrote:
>>>> On 4/13/2022 8:43 PM, Dave Froble wrote:
>>>>>
>>>>> Can you better define nested functions?  Then I can decide if
>>>>> Basic allows such.
>>>>
>>>> Functions declared inside functions (and therefore only available inside the
>>>> declaring function).
>>>>
>>>
>>> Ok, what is so neat about that?
>>>
>>> I cannot see the point, when if one wants to use a second function inside a
>>> first function, another external function should be
>>> callable. Haven't tried it recently.  Maybe I should.  Perhaps I
>>> should know what I'm talking about at least once a year.
>>>
>>> But I can see no reason to have a function defined inside another
>>> function.
>>>
>>
>> Encapsulation/Isolation
>
> Isolation from what?  You're writing the code, you decide what to write, I still 
> don't see the point.
>

When you write an application that's say 20,000 lines long, do you
write one great big monolithic function that's 20,000 lines long and
with sections of common code copy and pasted around in the application,
or do you split up the application into logical chunks and also include
common functions with a defined interface that can be called from
multiple points in your application ?

If it's the latter, you are already performing encapsulation and
isolation of functionality and nested procedures are just the
next step in that process.

Some reading:

https://en.wikipedia.org/wiki/Separation_of_concerns

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.



More information about the Info-vax mailing list