Re: LZ: NASR question
[Prev][Next][Index][Thread]
Re: LZ: NASR question
I'll I know is that i've ben told it can compile on some computers with
some software. Besides, why would J Xu make a mistake like that and NEVER
fix it?
Biya,
Will Stokes
8^)
_____________________________________________________
/ /|
/____________________________________________________/ |
| | |
| Will Stokes | |
| wstokes@geocities.com | |
| wstokes@vertex.ucls.uchicago.edu | |
| | |
| My Personal Homepage | |
| http://www.uic.edu/~hhstokes/will.htm | |
| | |
| The TI-85 Calculator Center | |
| (the website I maintain and update very often) | |
| http://www.geocities.com/SiliconValley/Pines/7360/ | |
| | /
|____________________________________________________|/
On Tue, 27 May 1997, Jim Reardon wrote:
> Well, it doesn't really matter what you use to compile it, there is no
> way it can jump relative that far (it is beyond the maximum # of bytes, I
> counted :) ).
>
> Jim Reardon
> jim.reardon@juno.com
> Viva La Mexico
> http://pages.prodigy.net/eviljim/
> We all come into the world the same way - naked, screaming, covered in
> blood. But if you live your life right, that kind of thing doesn't have
> to end there.
>
>
> On Mon, 26 May 1997 22:39:06 -0500 (CDT) Will Stokes
> <wstokes@vertex.ucls.uchicago.edu> writes:
> >this nasr *problem* I don't belive is actually a problem! What?! you
> >say?
> >Well, yes, I've never gotten it to compile withouth fixing that as
> >well
> >from jr to jp but I hear some version of tasm on certain machines
> >(maybe
> >it was just compiling stuff on macs with whatever their inferior
> >software
> >compiler was). but I have hear of many cases where it will compile
> >without
> >editing. dunno :)
> >
> > Biya,
> > Will Stokes
> > 8^)
> > _____________________________________________________
> > / /|
> > /____________________________________________________/ |
> > | | |
> > | Will Stokes | |
> > | wstokes@geocities.com | |
> > | wstokes@vertex.ucls.uchicago.edu | |
> > | | |
> > | My Personal Homepage | |
> > | http://www.uic.edu/~hhstokes/will.htm | |
> > | | |
> > | The TI-85 Calculator Center | |
> > | (the website I maintain and update very often) | |
> > | http://www.geocities.com/SiliconValley/Pines/7360/ | |
> > | | /
> > |____________________________________________________|/
> >
> >On Sun, 25 May 1997, Jim Reardon wrote:
> >
> >> There is one small bugger in the NASR.TXT on TiCalc, you need to
> >change
> >> one of the jr's to JUMP_() statements. I've always had to do this.
> >I do
> >> not suggest splitting the routines though, just leave them all
> >together.
> >>
> >> Jim Reardon
> >> jim.reardon@juno.com
> >> Viva La Mexico
> >> http://pages.prodigy.net/eviljim/
> >> We all come into the world the same way - naked, screaming, covered
> >in
> >> blood. But if you live your life right, that kind of thing doesn't
> >have
> >> to end there.
> >>
> >>
> >> On Sun, 25 May 1997 15:34:20 -0500 James <james@superb.net> writes:
> >> >I have a question about including NASR WARP in my assembly
> >programs.
> >> >Can
> >> >the routines be split into 3 or 4 seperate pieces? I'm asking this
> >
> >> >because
> >> >no matter where I put it in my code, I always get a "range of
> >relative
> >> >branch exceeded" from somewhere in the program. If I can't split
> >the
> >> >code,
> >> >where should I put it? Thanks for any help you can give me.
> >> >
> >> >James
> >> >
> >>
> >
> >
>
References: