<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to support-requests</title><link href="https://sourceforge.net/p/frameprocessor/support-requests/" rel="alternate"/><link href="https://sourceforge.net/p/frameprocessor/support-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/frameprocessor/support-requests/</id><updated>2003-07-21T16:53:59Z</updated><subtitle>Recent changes to support-requests</subtitle><entry><title>Generation for non-local directories</title><link href="https://sourceforge.net/p/frameprocessor/support-requests/2/" rel="alternate"/><published>2003-07-21T16:53:59Z</published><updated>2003-07-21T16:53:59Z</updated><author><name>Jens Engel</name><uri>https://sourceforge.net/u/userid-148645/</uri></author><id>https://sourceforge.net1b49f89f73291d6e64f2cd4b367e778611187738</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When processing frames that are not located in the current &lt;br /&gt;
working directory, it would be desirable to generate them &lt;br /&gt;
relative to the SPC file (or the FRAME file).&lt;/p&gt;
&lt;p&gt;The OUTFILE command contains normally a rather simple &lt;br /&gt;
or a relative pathname. When a relative pathname is used, &lt;br /&gt;
this pathname is expressed relative to the location of SPC &lt;br /&gt;
or FRAME file (depending where OUTFILE is defined).&lt;/p&gt;
&lt;p&gt;EXAMPLE:&lt;br /&gt;
# -- file:MySPC.spc&lt;br /&gt;
ADAPT MyFrameSubdir/MyFrame.frame&lt;br /&gt;
OUTFILE MyOutput/fileB.txt&lt;br /&gt;
...&lt;br /&gt;
# -- END-OF-FILE&lt;br /&gt;
sh&amp;amp;gt; cd ..&lt;br /&gt;
sh&amp;amp;gt; fp MySpcDir/MySPC.spc&lt;br /&gt;
CURRENT-OUTPUT:&lt;br /&gt;
generating MyOutput/fileB.txt&lt;br /&gt;
DESIRED-OUTPUT:&lt;br /&gt;
generating MySpcDir/MyOutput/fileB.txt&lt;/p&gt;
&lt;p&gt;RATIONALE:&lt;br /&gt;
A normal C/C++ compiler also behaves like this.&lt;br /&gt;
For example, searches for include files relative to the &lt;br /&gt;
location of the source file. It generates (BY-DEFAULT) the &lt;br /&gt;
output-file in the location of the source file, independent &lt;br /&gt;
from which directory it is called.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>DEFAULTS for Placeholders/Slots</title><link href="https://sourceforge.net/p/frameprocessor/support-requests/1/" rel="alternate"/><published>2003-07-21T16:25:44Z</published><updated>2003-07-21T16:25:44Z</updated><author><name>Jens Engel</name><uri>https://sourceforge.net/u/userid-148645/</uri></author><id>https://sourceforge.netc01018e6002b8684093b9a1ff364d9e85fd84d98</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be usefull to provide defaults for placeholders.&lt;br /&gt;
Normally, you need a RENAME command in the SPC file to &lt;br /&gt;
provide this for default and non-default values. It would &lt;br /&gt;
better to provide default values for placeholders in the &lt;br /&gt;
FRAME file.&lt;/p&gt;
&lt;p&gt;DESIRED-SYNTAX (Something like that):&lt;br /&gt;
&amp;amp;quot;SLOT&amp;amp;quot; PlaceHolderName OptionalDefaultValue&lt;/p&gt;
&lt;p&gt;EXAMPLE:&lt;br /&gt;
SLOT MySlot1 0x0815&lt;br /&gt;
SLOT MySlot2 &lt;/p&gt;
&lt;p&gt;NOTE: &lt;br /&gt;
The second case may cause a warning or an error of the &lt;br /&gt;
placeholder value is not supplied via RENAME in the SPC &lt;br /&gt;
file (ERROR_IF_NOT_SUPPLIED).&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>