hello,

can someone help me with the following rose 2000 C++ code generation problems:

- generating a prefix for filenames without manually entering the name
for every file: the rose98 solution (to use prefix$file or $name as the
filename property in the component view) does not seem to work anymore
Are there alternatives to specifying a hardcoded name for every component in the 
component
view ?

- rose generates type variableXnX in stead of the desired type variable[n] where 
variable[n]
: type is entered in Rose
 The same problem occurs when XXstart_addrX_XvoidX(void) is generated where
(*start_addr)(void) : (void) is entered and (void)(*start_addr)(void) is needed.
Is this a known problem and/or are there solutions or workarounds ?

- is there a way to tell rose which OS text file format to use ?  we
generate our code from windows, but there is also the requirement to
build in unix. Is there another way than to always run a converting
tool, or could i choose to let rose for windows generate unix style text files ?
The compiler and editor on windows accept unix style text files.

- we use the $CURDIR = & pathmap variable to be relocatable, but this
works only if the rose model is opened from windows explorer, and not if
you start rose first and than load the model (rose install directory is
used in stead of the model directory). It seems that the value is filled in at rose 
startup
iso when loading the model. Is there a way to make this value
independend of the way the model is loaded?

Thanks in advance,

Sven Biebaut


************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages: 
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************

Reply via email to