Hi all, Anyone knows why pypy.module._file.readinto uses a locally defined ‘os_read’ rather than rpython.rlib.rposix.c_read? It seems that the functions are defined almost the same way, except one uses rffi.CCHARP the other uses rffi.VOIDP, and the rposix.c_read has a more complete ExternalCompilationInfo. Whilst this doesn’t pose any problem to C backend, it does cause a small trouble in my Mu VM backend, as the two external functions have deemed different even though they are the same, thus causing a name conflict. The fix is simple in either case: use c_read in _file.readinto, or I just add a small hack in my backend. But I’d like to know why this is the case in the first place, is there a special reason for it?
Regards, John Zhang ------------------------------------------------------ John Zhang Research Assistant Programming Languages, Design & Implementation Division Computer Systems Group ANU College of Engineering & Computer Science 108 North Rd The Australian National University Acton ACT 2601 john.zh...@anu.edu.au<mailto:john.zh...@anu.edu.au>
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
