Index
> Compiler Internals > More info with 'Unexpected end of file error' ? |
| Author |
|
|
scientica 07 Aug 2004, 13:13
Yeah, IMO that would be anice featuer, but hard to implement in a "correct" way, I think one way could be eg, counting the "{" and "}" and say something (in addition to the unexpected oef like "{ at line # appears to be unmatched"
|
|||
07 Aug 2004, 13:13 |
|
|
mike.dld 07 Aug 2004, 15:19
I thought that compiler remembers what macro exactly he processes now.
|
|||
|
07 Aug 2004, 15:19 |
|
|
madmatt 07 Aug 2004, 17:53
Scientica:
Hard to implement? Just keep a record of which file you are processing, and current line in that file, and when an error occurs, simply print out the current informatoin. BTW, I got the error because I was missing an 'end if' in an 'if, else, end if' construct. One other suggestion I forgot to mention in my first post, would it be possible to give a total number of lines processed in an assembly project? This shouldn't be real hard to do. |
|||
|
07 Aug 2004, 17:53 |
|
|
decard 07 Aug 2004, 17:56
madmatt wrote: One other suggestion I forgot to mention in my first post, would it be possible to give a total number of lines processed in an assembly project? This shouldn't be real hard to do. It is implemented in Fresh.  |
|||
|
07 Aug 2004, 17:56 |
|
|
mike.dld 07 Aug 2004, 18:05
Try to assemble this:
Code: macro a [b] { if used c common db c end if } a s,d when writing Code: a s it's all right, this too Code: macro a [b] { common if used c db c end if } a s,d |
|||
|
07 Aug 2004, 18:05 |
|
|
madmatt 08 Aug 2004, 21:35
decard:
Hey, fresh assmbly IDE is lookin' pretty good!, especially building a GUI inteface for assembly. I'll have to play around with it more to see what there is to see. But so far, I like what I see! |
|||
|
08 Aug 2004, 21:35 |
|
< Last Thread | Next Thread > |
Forum Rules:
|