Linking files together in RTC
Accepted answer
Comments
Note that one reason RTC has explicitly chosen to not support this concept is that RTC gives you the option of automated control of what gets delivered into a stream. In particular, it runs process checks on every delivery, which would mean that in the case of a "linked" file, whenever a change is attempted to be delivered to that file, RTC would need to run all of the process checks of any stream that contained that link, to ensure that the process checks of those streams are not violated by this delivery. It was concluded that the cost (in both server load and end user confusion) outweighed the potential benefits.
2 other answers
What is the purpose of the link? What is the end result or benefit of the link between files? In RTC, you can group source code files into components and components into streams. Deliveries to the stream are done via changesets which group a set of source code files modified for a specific workitem like a defect or task.
Comments
In CMVC linked files between releases ( somewhat like RTC's stream ) meant that as long as those linked files were checked in to all the common releases, that particular file was guaranteed to have the exact same content (read: version) in all the releases. Choosing to "break" that link would result in a branch point on that particular file.