You will have to talk to SAS about how their engine works. Perhaps they are letting Oracle do the transformation from DECIMAL numbers into FLOATING point and that is why you are seeing slight differences in how non-exact binary values are represented.   If you want simulate work with decimal numbers in SAS then store them as integers and just remember where the decimal point belongs.  You can even make your own picture format to display the integers with the implied decimal point when printing. 177 proc format ; 178 picture mydollar low-high = '009.99' (multiplier=1) ; NOTE: Format MYDOLLAR is already on the library WORK.FORMATS. NOTE: Format MYDOLLAR has been output. 179 run; NOTE: PROCEDURE FORMAT used (Total process time): real time 0.00 seconds cpu time 0.00 seconds 180 181 data test; 182 input x @@; 183 put x= x= mydollar. ; 184 cards; x=100 x=1.00 x=123 x=1.23 x=4567 x=45.67 ... View more

Michael.Weiss wrote: The background is, I'm currently working on a correct syntax highlighter for SAS code and therefore I would like to highlight code as it is processed by the SAS code parser. If that is the case then I think your highlighter should at least consider your first two examples syntax errors.  Proper usage as mentioned is %STR or %NRSTR.  To make it easy on yourself flag any use of %BQUOTE or %NRBQUOTE (that appear in a macro) where the argument is not a macro variable reference as a "potential syntax error".   Does your syntax highligher know if it is looking at statements defined between %MACRO and %MEND. ... View more