Menu
▾
▴
#84 SDCCman additions
Changes for SDCCman.lyx (based on snapshot 4726):
- migration to lyx version 1.4.4 (format version 245)
- some additions to command line parameters and pragmas (although there are more command line parameters and pragmas to add and describe)
- more detailed description of inline and linked-in assembler ('51 related, but it was not labelled as such and I did not change on this)
- other minor changes
Included are:
- err_warn.txt - list of errors and warnings
- listerr.c - program to create this list from SDCCerr.c
Jan Waclawek
Logged In: YES
user_id=888171
Originator: NO
Jan, Frieder,
What to do with this? Close it because it was applied? Or is there something to be done with the error list? If so, what? My vote is either ignore it or include it in the manual. I see no point in keeping it in a separate file.
Maarten
Logged In: YES
user_id=1201677
Originator: YES
Maarten,
I assume you are talking about the list of errors and the program which created it (the .lyx file itself has been already upgraded by Frieder - although we still argue over it a bit...)
The point is, that the list of errors (this includes warnings) is changing. I'd even bet, that the appended list (which was created from the 2.6.0 sources) does not match the current list.
So, in the IDEAL case, I'd like to see the list to be automatically produced during the "nightly snapshot" and being imported to the documentation automatically... Of course I haven't the faintest idea how to accomplish this...
Jan
Logged In: YES
user_id=888171
Originator: NO
Yes, I meant the list of errors. Of course the list is changing, but so is the rest of the compiler ;) Documentation needs to be updated from time to time.
What is the use of a generated list? Is it to gain insight in what kind of errors and warnings SDCC can produce? Anyone can see that in the source code.
Is it to more thoroughly explain the errors? Then a generated list does not bring that info and it still must be added by hand. The generated list is probably a good starting point to be included in the documentation though. Then when new codes are added the documentation must be updated too.
Or is it only to make the severity level visible? For this automation should be enough.
So please define the purpose of the list first.
Logged In: YES
user_id=568035
Originator: NO
My opinion is not to put the list to the documentation, since it brings low additional value, but it brings a lot of troubles to maintaining it (see the "[ sdcc-Patches-1697136 ] SDCCman additions" thread in sdcc-devel mailing list). We already know that the documentation maintenance is out weakness :-( (Maybe Jan will change this...)
For the time being I suggest to put the script somewhere into the SVN, probably to support/scripts and remove the reference to err_warn.txt from sdccman.lyx.
The list can be included to the manual in the future if somebody finds and implements the way to do it automagically.
Borut
Logged In: YES
user_id=568035
Originator: NO
done as suggested in my previous post in svn revision #4761.
Borut