home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!europa.asd.contel.com!darwin.sura.net!haven.umd.edu!umd5!mac40-pg2.umd.edu!user
- From: de19@umail.umd.edu (Dana S Emery)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: Help with Think Pascal,C
- Message-ID: <de19-230792103455@mac40-pg2.umd.edu>
- Date: 23 Jul 92 14:53:53 GMT
- References: <Brr1Ep.ILM@csn.org>
- Sender: news@umd5.umd.edu
- Followup-To: comp.sys.mac.programmer
- Organization: Personal
- Lines: 32
-
- In article <Brr1Ep.ILM@csn.org>, erich@csn.org wrote:
- > ....
- > I am a skilled C programmer, but I have never written anything in
- > Pascal. SO essentially I need to know which is easier:
- >
- > Mixing Think C and Think Pascal modules
- > OR
- > Learning Pascal after knowing C very well.
-
- Eric
-
- First, you dont say whether you are planning to use objects, but you should
- know that (according to Symantec) C objects and Pascal objects *dont* mix
- at all. The dynamic binding mechanisms are different, so if you are going
- to add C code to the Pascal project, the C code must not use objects from
- either side.
-
- Second, you are going to have to write interfaces for both the Pascal and
- the C portions, so that each knows how to reference the other. This is not
- easy to do or to debug, *you* are totaly responsible for making sure that
- this 'glue' doesnt *lie* on either side, as neither compiler has any way of
- helping you. I would think it a significant impediment for someone who is
- ignorant of one of the 2 languages.
-
- I would recommend that you learn Pascal-its not so hard, and you are going
- to need that knowledge to understand the Pascal code which you are
- modifying. You might want to use some of your C thinking skills by
- pseudo-coding in C, then translating that to Pascal-eventually you will
- find yourself fluent in the new language, and can cease with the crutch.
- --
-
- Dana S Emery <de19@umail.umd.edu>
-