Re: Removing or replacing *inzsr with Dspecs

Just to be clear - these tools I suggested are things I'd use AFTER working things out manually - I hinted at that in my offering, but it needs to be said more distinctly, I guess.

As an example, I know how to convert subroutines to procedures - AND Craig's tool for doing that conversion showed me an interesting additional way to do this - yes, I could have read up on it and tried it - but I probably wouldn't have had occasion to do so. His approach gives a nice generic methodology. Which I now forget the details of - seems like it had something to do with a keyword on the prototype that we don't often see mentioned.

Now i also believe that there is almost nothing better for learning than to type examples out yourself - far better than copy/paste. Bach is said to have learned composition by copying works of Vivaldi by hand - something about that, the music or code or whatever seems to flow up the arm to the brain.

Cheers
Vern

On 6/10/2014 1:32 PM, John Yeung wrote:

On Tue, Jun 10, 2014 at 2:09 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

Thinking in general about /educational/ value, I find myself taking the
contrarian view when it comes to automated conversions. I don't believe
that there is much educational value in seeing EXSR CHECKCUST converted
to CALLP CHECKCUST.

I don't think your view regarding education is contrarian. Most folks
would recommend working by hand, at least while learning. (I count
only two people so far who recommended automated tooling, and one of
them didn't mention anything about learning, only about
standardization.)

To his credit, OP did say his plan was to do this project manually.

John