From: SourceForge.net <no...@so...> - 2011-04-28 08:09:13
|
Bugs item #3293347, was opened at 2011-04-26 23:36 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=3293347&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: linker Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Brian Ruthven (u6c87) Assigned to: Nobody/Anonymous (nobody) Summary: linker requires .lk file, docs say .lnk Initial Comment: Somewhere between 6382 (Apr 7th) and 6468 (Apr 26th), the linker was changed to only accept the filename extension ".lk". I'm not sure why this is, but it deviates from the documentation (sdas/dos/asmlnk.txt) which states [ in -f file mode ] "the commands are input from the specified file (extension must be .lnk).". It looks like this was introduced by Revision 6445, where lklex.c was modified to change "lnk" to "lk". In addition to this deviating from the docs, it also deviates from the usage output which still states "file[.lnk]" as the source for the "-f" argument. Whilst I don't really mind which extension is used, the documentation and implementation should match. I'm not sure how to map this back to a "bug" number which was fixed, so I can't see the rationale behind the change. SDCC versions involved: Works with .lnk as documented: SDCC : z80 3.0.2 #6382 (Apr 7 2011) (Solaris i386) Requires .lk extension: SDCC : z80 3.0.2 #6468 (Apr 26 2011) (Solaris i386) Error produced with the later version: $ bin/sdldz80 -nf project.lnk ?ASlink-Error-<cannot open> : "project.lk" *** Error code 3 ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2011-04-28 10:09 Message: Hello Brian, I changed it to .lk but still have to adapt the documentation. The reason is that Windows, even with the option to show extensions, hides this extension because it thinks this is a link to another file/folder. It is also my intention to use whatever extension is privided and default to .lk when none is given. Maarten ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=3293347&group_id=599 |
From: SourceForge.net <no...@so...> - 2011-04-28 08:28:45
|
Bugs item #3293347, was opened at 2011-04-26 22:36 Message generated for change (Comment added) made by u6c87 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=3293347&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: linker Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Brian Ruthven (u6c87) Assigned to: Nobody/Anonymous (nobody) Summary: linker requires .lk file, docs say .lnk Initial Comment: Somewhere between 6382 (Apr 7th) and 6468 (Apr 26th), the linker was changed to only accept the filename extension ".lk". I'm not sure why this is, but it deviates from the documentation (sdas/dos/asmlnk.txt) which states [ in -f file mode ] "the commands are input from the specified file (extension must be .lnk).". It looks like this was introduced by Revision 6445, where lklex.c was modified to change "lnk" to "lk". In addition to this deviating from the docs, it also deviates from the usage output which still states "file[.lnk]" as the source for the "-f" argument. Whilst I don't really mind which extension is used, the documentation and implementation should match. I'm not sure how to map this back to a "bug" number which was fixed, so I can't see the rationale behind the change. SDCC versions involved: Works with .lnk as documented: SDCC : z80 3.0.2 #6382 (Apr 7 2011) (Solaris i386) Requires .lk extension: SDCC : z80 3.0.2 #6468 (Apr 26 2011) (Solaris i386) Error produced with the later version: $ bin/sdldz80 -nf project.lnk ?ASlink-Error-<cannot open> : "project.lk" *** Error code 3 ---------------------------------------------------------------------- >Comment By: Brian Ruthven (u6c87) Date: 2011-04-28 09:28 Message: Thanks for the explanation. At least I know it's not a glitch, and I can modify my project accordingly. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2011-04-28 09:09 Message: Hello Brian, I changed it to .lk but still have to adapt the documentation. The reason is that Windows, even with the option to show extensions, hides this extension because it thinks this is a link to another file/folder. It is also my intention to use whatever extension is privided and default to .lk when none is given. Maarten ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=3293347&group_id=599 |
From: SourceForge.net <no...@so...> - 2011-05-03 10:11:24
|
Bugs item #3293347, was opened at 2011-04-26 23:36 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=3293347&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: linker >Group: fixed >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Brian Ruthven (u6c87) >Assigned to: Maarten Brock (maartenbrock) Summary: linker requires .lk file, docs say .lnk Initial Comment: Somewhere between 6382 (Apr 7th) and 6468 (Apr 26th), the linker was changed to only accept the filename extension ".lk". I'm not sure why this is, but it deviates from the documentation (sdas/dos/asmlnk.txt) which states [ in -f file mode ] "the commands are input from the specified file (extension must be .lnk).". It looks like this was introduced by Revision 6445, where lklex.c was modified to change "lnk" to "lk". In addition to this deviating from the docs, it also deviates from the usage output which still states "file[.lnk]" as the source for the "-f" argument. Whilst I don't really mind which extension is used, the documentation and implementation should match. I'm not sure how to map this back to a "bug" number which was fixed, so I can't see the rationale behind the change. SDCC versions involved: Works with .lnk as documented: SDCC : z80 3.0.2 #6382 (Apr 7 2011) (Solaris i386) Requires .lk extension: SDCC : z80 3.0.2 #6468 (Apr 26 2011) (Solaris i386) Error produced with the later version: $ bin/sdldz80 -nf project.lnk ?ASlink-Error-<cannot open> : "project.lk" *** Error code 3 ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2011-05-03 12:11 Message: I fixed the documentation (asmlnk.txt, asxhtm.html, sdld -h) and also implemented the use of the provided extension in revision #6476. ---------------------------------------------------------------------- Comment By: Brian Ruthven (u6c87) Date: 2011-04-28 10:28 Message: Thanks for the explanation. At least I know it's not a glitch, and I can modify my project accordingly. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2011-04-28 10:09 Message: Hello Brian, I changed it to .lk but still have to adapt the documentation. The reason is that Windows, even with the option to show extensions, hides this extension because it thinks this is a link to another file/folder. It is also my intention to use whatever extension is privided and default to .lk when none is given. Maarten ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=3293347&group_id=599 |