@ATTACK - @Return.Value
RTP Series - RTP5
RTP Series - RTP21
@ATTACK - @Null.Eval
Reader's Clinic - EVAL
What's New (and un(der)documented!) In 2.12
Catalyst
@ATTACK - @Ans
QTIPS - Compiling Work around on runtimes
QTIPS - Potential Problem When Using @ANS
@ATTACK - @Modal
Reader's Clinic - Capture Command and Captured Keystrokes
Catalyst
Popups
Catalyst Tips
QTIPS - NoRead
Reader's Clinic - EVAL
QTIPS - New Catalyst Option
VERBatim - V15
QTIPS - Compiling Work around on runtimes
Reader's Clinic - EVAL
QTIPS - Compiling Protection Code
RTP5 and RTP51
Compiling 64K on a Shoestring by Blaise Wrenn (LexStat Systems Ltd)
QTIPS - Using @Upper.Case and @Lower.Case with Foreign Languages
@ATTACK - @Lower.Case
@ATTACK - @Upper.Case
Sorting out Collation Sequences by Mike Pope
Reader's Clinic - Different Id Same Record
Reader's Clinic - Scaled Masked Decimal Conversions
Base Conversions
User Defined Conversions
Reader's Forum - Numeric Precision in R/Basic - Hal Wyman
Reader's Clinic - Preventing Records Being Amended
QTIPS - Finding/Replacing Spaces With The Editor
Reader's Clinic - Scribe Replace Processes in Window
Reader's Clinic - Page Marks in Windows

RevMedia FKB

DocumentV3I1A8
TitleReader's Clinic - EVAL
KeywordsEVAL
CATALYST
COMPILE
TextSimon Rayne faxed recently WITH details of a problem he was having WITH the
EVAL STATEMENT It seemed that the STATEMENT following prints the value "1"
instead of 2!

eval @ans = 1 ; call catalyst("C" "@ans=2") ; print @ans

This is because neither EVAL nor CATALYST call the preprocessor called by
the COMPILE STATEMENT (the routine responsible for upper case conversion
INSERTS etc) Thus the @ans = 2 fails to compile correctly Mr Rayne points
out that the fix to this is to use uppercase! (i e replace @ans WITH @ANS)


(Volume 3 Issue 1 Page 15)
[revmedia/copyrigh.htm]

Page last modified: 08/02/03