1988
DOI: 10.1109/32.6138
|View full text |Cite
|
Sign up to set email alerts
|

Naming and binding in a vertical migration environment

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...

Citation Types

0
1
0

Year Published

1989
1989
1989
1989

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(1 citation statement)
references
References 9 publications
0
1
0
Order By: Relevance
“…The approach taken in the referenced project was very general allowing the migration of any callable routine from the software regardless of what the migrated routine itself might call. In order to have such general ability to assign software functionality to microcode or hardware, there must be an extremely well-designed set of interfaces between the hardware, firmware and software [9].…”
mentioning
confidence: 99%
“…The approach taken in the referenced project was very general allowing the migration of any callable routine from the software regardless of what the migrated routine itself might call. In order to have such general ability to assign software functionality to microcode or hardware, there must be an extremely well-designed set of interfaces between the hardware, firmware and software [9].…”
mentioning
confidence: 99%