[Info-vax] Development Tooling (was: Re: Opportunity for VSI?)

[Stephen Hoffman]

On 2018-12-17 05:41:28 +0000, Phillip Helbig (undress to reply said:

> In article <pv6m04$c9f$1 at dont-email.me>, Stephen Hoffman 
> <seaohveh at hoffmanlabs.invalid> writes:

>> As you're almost certainly referencing compilers there, that's not been 
>> a product differentiator in recent years,
> 
> What about Fortran 2018?

What about it?  VSI is not going to create a bespoke and 
performance-competitive Fortran 2018 compiler.

Not going to happen.

VSI doesn't have the schedule or budget or staff for that.

The bespoke and performance-competitive compiler effort won't provide 
enough incremental revenue over grafting the existing Fortran front-end 
onto LLVM, and of adopting and contributing to flang as that evolves 
forward.

>> You've indicated you're an EDT user.  Go try LSEDIT.  See how that  
>> changes your approach to source code development.  The keypad is that 
>> of EDT (or EDT keypad can be selected), so what's new is the command 
>> line interface in the editor, and a few shortcuts such as ^F and ^G in 
>> the diagnostic review window after a COMPILE /REVIEW command.
> 
> I've used LSEDIT a few times.  I have a huge number of macros in EDT by 
>  now.  I tend to have code in one window, make changes, save them (yes, 
>  via an EDT macro), compile, link, and run in another, and so on.  
> Enough  for me.

Sure.  It works.  But because you haven't used new tooling—much like 
the glue-code that OpenVMS apps tend to accrete—the effort in your 
existing approach is invisible to you.

 I certainly hadn't recognized glue code as an issue, until I saw folks 
working to reduce that.  Nor recognized the down-revision tooling until 
I'd used newer tooling, for that matter.




-- 
Pure Personal Opinion | HoffmanLabs LLC