RE: Re: Fullscreen application Specs

Paul
 
I have one more routine to finish in assembler before I can say I have a
real ALPHA version.
Just have to add the saving of the file.
 
Once I get that done - I will have accomlished my initial GOAL of a
"MULTI_TASKING" - "FULL_SCEEN" environement and a sample usable working
application 'EDIT/BROWSE' -  in the time frame I allocated to this - One
Month. +-. 
( I am a super programmer :-) - but even for me, the amount of work here,
and the success I have had so far is more than I expected)
 
At the rate I am going it should take me less than two or three days
depending on what the "WIFE" has planned for me to finsh the file saving
routines.
 
I am putting more effort into the EDIT/BROWSE application part than I
planned, because I want it to be a useful tool which is definitely missing
on the Vanilla VM/370 platform. 
 
Truth is I didn't analyse the requirements enough when I started (just a 10
line editor for a rexx script ;-) so I ended up redoing a lot of the
routines after I got new requirements from the Group.
 
Andy can make it part of the 6-pack if he wants and I think that will
improve the User experience for everyone.
 
But as for "C"----
 
Once I have the ALPHA version working with all the Basic functions I will
play around with the "C" -Not that this application needs it, but as a
learning experience for integrating other applications into the environment
I am creating.
 
I am counting on you giving me advice and help when I get to that stage.
 
Roc
 
 


  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of
kerravon86
Sent: Thursday, August 05, 2010 09:50 
To: [email protected]
Subject: [H390-VM] Re: Fullscreen application Specs


  

--- In [email protected] <mailto:H390-VM%40yahoogroups.com> , "Rocky"
<rocsystems@...> wrote:
>
> The way I wrote "C" it was almost assembler in any case.

As it will be on VM too.

> I'm pretty sure that most old timers work the same way -
> If they don't have a tool box then they are not really pros.

I have a toolbox of utilities, but nothing that
would really help with something like what you're
doing.

Then again PDOS was a whole lot easier just having
a C library to lean on.

> But "C" is fine - I never wrote it on the MF so 
> I am a little apprehensive.
> When I have a BUG in assembler I know its my BUG
> A bug in "C" - I'm not sure.

I totally understand the apprehension - but please
try generating a small C function:

int addnums(int a, int b)
{
return (a + b);
}

and make sure you compile with optimization on
(-Os) and I suspect that you'll be perfectly
happy taking ownership of that generated code.

From then on everything's just a variation of
the theme. :-)

Surely you can at least try it once, in 3 * 10-minute
intervals? First 10 minutes is trying to find the
compiler on your system and then reporting here
what didn't work. Second 10 minutes is running it
and asking here a question about R13. Third 10
minutes is calling it from assembler and saying
"Who would've believed it? It actually works!". :-)

BFN. Paul.

> From: [email protected] <mailto:H390-VM%40yahoogroups.com>
[mailto:[email protected] <mailto:H390-VM%40yahoogroups.com> ] On
Behalf Of
> kerravon86
> Sent: Wednesday, August 04, 2010 19:09 
> To: [email protected] <mailto:H390-VM%40yahoogroups.com> 
> Subject: [H390-VM] Re: Fullscreen application Specs
> 
> 
> 
> 
> --- In [email protected] <mailto:H390-VM%40yahoogroups.com>
<mailto:H390-VM%40yahoogroups.com> , "Rocky"
> <rocsystems@> wrote:
> >
> > There is a lot of app logic involved here
> 
> And you're still not tempted to write any of
> this in C?
> 
> While you personally are clearly very productive
> in assembler, anyone else trying to debug a
> problem or make minor improvements is going to
> give up before they even start.
> 
> I see all assembler code on a dangerous road to
> an orphanage. It's a dying art (a fact hidden
> by the unusual nature of participants in these
> Herc groups), while C programmers are 
> permanently available at a dime a dozen.
> 
> BFN. Paul.
>