{"title":"外部函数和公共Lisp","authors":"H. Sexton","doi":"10.1145/1317273.1317275","DOIUrl":null,"url":null,"abstract":"The language Common Lisp is a standard dialect of Lisp which has been implemented on a wide range of machines by a variety of commercial and academic groups. One serious flaw in the Common Lisp standard, at least to many Common Lisp users on \"general-purpose\" hardware,1 is the lack of an defined foreign function interface, or FFI. The subject of this note is a discussion of FFI's for three different Common Lisp systems on engineering workstations and some thoughts on what foreign function interfaces ought to look like.","PeriodicalId":262740,"journal":{"name":"ACM SIGPLAN Lisp Pointers","volume":"02 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1987-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"9","resultStr":"{\"title\":\"Foreign functions and common Lisp\",\"authors\":\"H. Sexton\",\"doi\":\"10.1145/1317273.1317275\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The language Common Lisp is a standard dialect of Lisp which has been implemented on a wide range of machines by a variety of commercial and academic groups. One serious flaw in the Common Lisp standard, at least to many Common Lisp users on \\\"general-purpose\\\" hardware,1 is the lack of an defined foreign function interface, or FFI. The subject of this note is a discussion of FFI's for three different Common Lisp systems on engineering workstations and some thoughts on what foreign function interfaces ought to look like.\",\"PeriodicalId\":262740,\"journal\":{\"name\":\"ACM SIGPLAN Lisp Pointers\",\"volume\":\"02 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1987-12-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"9\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"ACM SIGPLAN Lisp Pointers\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/1317273.1317275\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"ACM SIGPLAN Lisp Pointers","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/1317273.1317275","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
The language Common Lisp is a standard dialect of Lisp which has been implemented on a wide range of machines by a variety of commercial and academic groups. One serious flaw in the Common Lisp standard, at least to many Common Lisp users on "general-purpose" hardware,1 is the lack of an defined foreign function interface, or FFI. The subject of this note is a discussion of FFI's for three different Common Lisp systems on engineering workstations and some thoughts on what foreign function interfaces ought to look like.
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
