[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: more 2.1
- To: email@example.com
- Subject: Re: more 2.1
- From: David.Lamkins@p14.f640.n101.z1.fidonet.org (David Lamkins)
- Date: Sat, 16 May 92 11:45:59 EDT
> While were on the subject of Think C and MCL 2.1 requests, how about a
> FF interface for ThinkC?
Up> Symantec has been threatening to include a ThinkC -> MPW library
Up> translator for a while.
Up> When I called the Think C folks a year ago, they said that
Up> Think C could make Think Pascal projects and Think Pascal has an MWP
Up> library generator. So there IS a way to get to something that MCL's FF
Up> interface likes.
Up> Unless Symantec starts including a Think C -> MPW library tool, I'd
Up> much rather be able to link directly from a Think C project file, but
Up> the Think C folks did not sound eager to divulge their file format,
Up> leaving us to reverse engineer it: not desireable. I sent a letter
Up> (again a year ago) to the Think C marketing manager urging him to
Up> provide a public domain Think C -> MPW library converter and telling
Up> him that it was a question of packaging, not technology, but I never
Up> got a response.
Up> Maybe if a lot of people who use both Think C and MCL would bug
Up> Symantec about it, we could get the Think C -> MPW library converter
Up> from them and make things easier for everyone.
I'm not sure what all the fuss is about. If you can build a THINK Pascal
from a THINK C project, you should be able to load that _directly_ using MCL's
FF interface. A THINK Pascal library has the _same_ file format as an MPW
file - in fact, it even has the same type signature ('OBJ ').
I get the impression from the original message (and subsequent follow-up) that
people are assuming you have to convert a THINK Pascal library to MPW format
- this just isn't so! If you have any doubts, try this: Build a THINK Pascal
library using THINK C, then look at it using MPW's DumpObj tool.
--- Through FidoNet gateway node 1:16/390