... vars=FN p(23627): LET defadd=23563
32 LET udg=FN p ... ,FN d(deftmp): POKE nxtlin+8,FN d(deftmp+9):
POKE defadd,FN ... l(deftmp): POKE defadd+1,FN h(deftmp)

... variable was found in the DEFADD area then Stack Variable is ... later post:
LET m$=FN m$("S",0,"-",16384+2048 ... s$, and:
LET m$=FN m$("-",16384+2048,"S",0 ... 's occurred to me that FN m$() could handle both string ...

... variable was found in the DEFADD area then Stack Variable is ... later post:
LET m$=FN m$("S",0,"-",16384+2048 ... s$, and:
LET m$=FN m$("-",16384+2048,"S",0 ... 's occurred to me that FN m$() could handle both string ...

... s an updated version of FN m$() which handles string slicing ...
[code]
2 DEF FN p(a)=PEEK a+256 ... (v/256):
DEF FN d(a)=a-(64 AND ... br />
13 LET nl=FN p(23637): RETURN:
REM ...
16 POKE nl+5,FN d(PEEK da): POKE nl ...

...
[/CODE]

DEFADD is the address of arguments ... "0000000000000000" inside the DEF FN, so if you change it ... 7 DEF FN h(h$)=16*FN n(h$(1))+FN n(h ... /> 2030 PRINT "FN b$(j)",FN b$(j,FN x(a$))
FN x(a$).

... reason for combination with DEF FN.
Still treasures can be ... useful DEF FN because all variables are vectorized from DEFADD and because ...

... p, defined as a DEF FN plus a *small* (117 ...
[CODE]
1 DEF FN i(n,t$,s$)=USR ... /> 5b00 dd2a0b5c LD IX,(5c0b) ; DEFADD
5b04 010000 LD BC ...
[CODE]
1 DEF FN i(n,t$,s$)=USR ... /> 3 DEF FN h(h$)=16*FN n(h$(1))+FN n(h ...

Here's a recursive DEF FN INSTR one-liner, cunningly contrived ... it in a separate function "FN c(c,o$)" didn't ... I thought that maybe "DEF FN c()=c+LEN o$-1 ... the VARS area rather than DEFADD and there they are not ... />
[code]
4 DEF FN i(w$,o$,c)=

... /> Main proc
ld hl,(DEFADD)
inc hl
inc ... byte expressions, write:
[code]FN z(first_expression,second_expression,"&")[/code ... ]FN z(FN z(a, FN z(b,0,"~"),"&"),FN z(b, FN z ...

... ]

Yes, using FN so that the USR function ... pick up parameters from the DEFADD area simplifies the syntax, ... only specified in the DEF FN. Your code is easy ... nested function rather than just FN z(a,b,"^").
... I could use DEF FN a(a$)=USR address+ ...

... $ ... + VAL$ bit, the FN j$ bit and the """""" bit ... byte from memory;
* ("FN j$("+STR$ (s+1)+","+STR ... decrements the counter and calls FN j$(s,l) again ... ) and then VAL$ sees "FN j$((56169),(7))" and so ... iteration creates a new DEFADD area for its version ...

... />
Using a separate DEFADD area to hold single letter ... assignments won't work but DEFADD variables will still be ... subscripted, as SCANNING deals with DEFADD variables differently and doesn't ... then string functions such as FN s$(), STR$ and CHR$ ...

...
Using a separate DEFADD area to hold single letter ... won't work but DEFADD variables will still be ... as SCANNING deals with DEFADD variables differently and doesn't ... then string functions such as FN s$(), STR$ and CHR ... use of the DEF FN memory move. If I ...

... sets up a dummy DEF FN of a$:

[CODE ... DEF FN[/CODE]
Next we need to alter the DEFADD (23563 ... an empty string and the DEFADD system variable to its default ...

Any DEF FN which has parameters works in ... v.15; eg:
DEF FN p(a)=PEEK a+256 ... called because the DEFADD variables area for the FN does not get ... passing syntax, so every DEF FN gets treated as having no ...

... Bunny;619146]Any DEF FN which has parameters works in ... because the DEFADD variables area for the FN does not ... syntax, so every DEF FN gets treated as having no ...
By the way, DEF FN bug was caused by the ... $CE (which is DEF FN) in the string sometimes). ...

... USR call in a DEF FN and calling it with a ... .
[code]
10 DEF FN a(s$)=USR 4e4
FN a(s$)
[/code]

The address of DEFADD ...

... br /> [code]
DEF FN l(c,t,b,a ...
...
LET bc=FN l(column,top,bottom,attributes ... SL2: ld ix,(23563) ;IX=(DEFADD)

NEXTROW:ld b ... /> [code]
1 DEF FN l(c,t,b,a ... USR 23296:
DEF FN r(a,z)=a+INT ...

This routine (48 bytes) provides a BASIC replacement for STR$ which fixes those two bugs; use "FN s$(numeric_expression)" instead of "STR$ numeric_expression". I copied the ROM's method used in CIRCLE & DRAW for checking -1

... :
[code]
100 DEF FN a(a,b,c,d ... are using the DATADD and DEFADD system variables here. Can you ...

... are using the DATADD and DEFADD system variables here. Can you ... define a FUNCtion like DEF FN A(p1,p2,p3)=usr ... the lines under the DEF FN were read as procedure that ... the procedure like a RANDOMIZE FN A(1,2,3)

... are using the DATADD and DEFADD system variables here. Can you ... hidden variables space allocated to FN a(). Using the function will ... strings) in that space. Setting DEFADD to point to it enables ... the variables are global as DEFADD is only set once. To ...

... index parameters:
REM f = FN x() variables address; d = ... 256*PEEK (a+1): DEF FN c()=FN p(23621)
9899 ... /> POKE 23563,FN g(defa): POKE 23564,FN h(defa):
REM restore VARS & reset DEFADD, retaining compacted DATA array & ...

... returns updated values for the FN (a) parameters to maintain ... had to reset DEFADD before returning and so the FN (a) parameters ... RESTORE FN c()+k1: POKE dh,k0: REM disable DEFADD redirection
923 FOR h=kC-k3 TO kC: POKE FN ...

... br /> [code]
2 DEF FN p(a)=PEEK a+256 ... a
30 DEF FN a$(a$)=""
REM ... /> REM 23563 = DEFADD = address of DEF FN parameters
31 ... RESTORE 30: LET d=FN p(23639)+9:
... POKE 23563,FN l(d): POKE 23564,FN h(d): ...

... .
[code]
10 DEF FN p(a)=PEEK a+256 ... ):
CLEAR 65367: LET UDG=FN p(23675): LET k0=NOT ...

[code]; THE SCANNING VARIABLE ROUTINE
org 0x26c9
s_letter:
call look_vars ; check for matching entry
jp c, report_2 ; error if not
call z, stk_var ; stack parameters
ld a, (flags) ; get flags
cp ...

... />
[code]
2 DEF FN o(f$)=USR 32768
20 LET exists=FN o(f$+CHR$ 255)
ld hl,(23563) ;(DEFADD) holds start of FN o(f$) arg