• Subject: Re: Not keying decimal points
  • From: Douglas Handy <dhandy1@xxxxxxxxxxxxx>
  • Date: Mon, 29 Jan 2001 16:10:53 -0500

Dave/Lance/et al,

>I don't have a solution, but I do have a work-around for emulators 

This is a visually slick solution for the problem of Field- changing the zone of
the last digit, but it still doesn't adress Lance's requirement for an assumed
decimal point when not explicitly keyed.

TTBOK, there is no system support for this.  It can only be implemented via
alpha fields and user code.  Note that the macro technique is still applicable
in this case.  You can have implied decimal points or field editing, but not

One message, however, suggested the S/36 supported this.  It did not, except in
user code.  Traditional numeric input fields on the S/36 were not edited.  They
did use an implied decimal point, but did *not* edit the field on output.  And
in fact, you *couldn't* key the decimal point in traditional $SFGR input fields,
which were signed numeric fields.

I got tired of that on the S/36, and back in '87 switched all my S36 code to use
alpha fields and a routine to de-edit input (with an implied decimal point) and
show edited output.  This was a pain on the S/36 at the time, because I didn't
even have CALL/PARM support.  I love service programs these days...

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.