![]() |
Telelogic Rhapsody (steve huntington) | ![]() |
Topic Title: Language independent profiles in Rhapsody? Topic Summary: Created On: 27-Jul-2004 20:28 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Folks,
a question from a customer using Rhapsody in C: * Is there a C-Version of the SPT profile shipped with Rhapsody v5.0.1? Profiles are more or less packages (.sbs files), which can be loaded with a model automatically. Now Rhapsody stores some archive language information with each package... saying that the SPT profile is C++ only. Now a question from myself: * Is there a way to create archive language independent profiles? In the Property area, we can distinguish between site.prp, siteC.prp and siteC++.prp, ... and language independent properties can be saved in the site.prp. There seems to be no such concept for profiles... true? Is there a plan to have this? Or does it not make sense to have generic profiles at all? Does not look exceptional to think about having profiles, which contain common and language dependent parts... Thanks, Martin. |
|
![]() |
|
![]() |
|
Martin
Interesting point... In practice, the SPT profile is completely language independent, however, since it was created under RiC++, it has a C++ "stamp". So for the interim you should use the migration backdoor to simply get it into RiC. And yes, it makes tons of sense for profiles to be language independent. In general we are looking into making this entire model language-binding more flxible post Rhapsody 6.0, and at least address this "reusable" profiles issue. Eran |
|
![]() |
|
![]() |
|
Hi,
I know that this thread is a couple of years old, but if you open the Rhapsody file with an editor, change the C++ (or C) on the first line to an * then the profile becomes generic. I used this method to create a generic profile from an RiC generated profile. Ian |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.