3 ms·
I downloaded and played with IE for Solaris, but I didn't use it for day to day browsing. One interesting thing that I recall from it was that it had .so files
by dunham 11y ago
I downloaded and played with IE for Solaris, but I didn't use it for day to day browsing. One interesting thing that I recall from it was that it had .so files that corresponded to each of the windows DLLs. So it looked like they had some sort of framework for porting windows code to Unix.
- ams6110 11y agoIE originated as Spyglass Mosaic, formerly NCSA Mosaic, a unix browser. So it was more like they ported unix code to Windows.
- deleted 11y ago[deleted]
- teddyh 11y agoSpyglass did not use any of the code from NCSA Mosaic¹. ① http://ericsink.com/Browser_Wars.html http://ericsink.com/Browser_Wars.html
- thwarted 11y agoThere used to be a page from the IE for UNIX porting team[0] that talked about the challenges of a direct port. Last I checked, only a copy of the content could be found on a mailing list post[1]. There's some interesting stuff in there. This one always seemed like a weird problem: Global variables in Win32 dynamic-link libraries (DLLs) are visible across processes, so it is important that developers are careful that these globals do not conflict with any variables within the Unix shared libraries. At least in the way it is presented. What does variables in DLLs being visible across processes on Windows have to do with variables in other libraries? Of course they need to be uniquely referenced. [0] http://tech.slashdot.org/story/98/11/17/1624254/microsoft-programmers-on-porting-to-x http://tech.slashdot.org/story/98/11/17/1624254/microsoft-pr... [1] http://www.linux.cz/pipermail/linux/1999-September/051669.html http://www.linux.cz/pipermail/linux/1999-September/051669.ht...