gnupic: Re: [gnupic] gpsim/gpasm assertions
Subject:
Re: [gnupic] gpsim/gpasm assertions
From:
Craig Franklin ####@####.####
Date:
27 May 2005 02:56:10 +0100
Message-Id: <42967EA2.6050307@users.sourceforge.net>
Scott Dattalo wrote:
>On Mon, 2005-05-23 at 09:26 +0100, Chris Emerson wrote:
>
>
>>On Sat, May 21, 2005 at 09:38:05AM -0700, Scott Dattalo wrote:
>>
>>
>>>The syntax in gpasm is:
>>>
>>> .direct "A" "expression"
>>>
>>>
>>[...]
>>
>>
>>>If the expression evaluates to true, then gpsim will halt.
>>>
>>>
>>Do you mean that, or do you mean gpsim halts when the expression is
>>false (the normal sense of assertions)?
>>
>>
>
>Oops - you're correct, my assertion about assertions was false. What I
>meant to say is that gpsim halts if the expression evaluates to *false*.
>
>
>
Version 4.0 of the COD file spec says this:
If expression is true (non-zero) then execution halts and a message is
printed to standard error containing the following information:
- name of the source code file containing the triggered assertion
- source line number of the triggered assertion
>I've also just checked in two new features:
>
> -- breakpoint expressions are now displayed along with breakpoints.
> If you write:
>
> .assert "var2==6"
> nop
>then the displayed break will look something like:
>
>1: p16f873 Execution at 0x0075
> Expression:(var2==6)
>
>
> -- breakpoints can now have messages associtated with them.
> If you enter the command:
>
>gpsim> break e 0x73, "a quoted string for a break point"
>
>and then display the break:
>
>5: p16f873 Execution at 0x0073
> Message:a quoted string for a break point
>
>There's an issue with using quoted strings with assembly assertions;
>currently gpasm does no parsing of assertion text (or any .direct type
>text for that matter) and thus it's currently not possible to specify a
>quote character as part of the string. I suppose the text parsing can be
>part of gpsim instead... I'm not sure which is better; should gpsim or
>gpasm parse string escapes?
>
>
>
gpasm can convert the escape characters, if that is best. I am not
worried about the quotes. What about the other characters (\t \n \r
...)? Are there any problems with converting those? It has to be all
or none.
>Scott
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>
>
>
