Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!yale!zip.eecs.umich.edu!newshost.marcam.com!news.mathworks.com!gatech!howland.reston.ans.net!Germany.EU.net!EU.net!sun4nl!cvitoa!jelle
From: jelle@cvi.ns.nl (Jelle Wolthuizen)
Subject: Re: Smalltalk to C generator?
Message-ID: <1995May4.144516.26902@cvi.ns.nl>
Date: Thu, 4 May 1995 14:45:16 GMT
References: <1995May4.084315.16971@cvi.ns.nl> <3oaaqm$o1f@isnews.is.s.u-tokyo.ac.jp>
Organization: Centrum Voor Informatieverwerking, Utrecht, The Netherlands
X-Newsreader: TIN [version 1.2 PL1]
Lines: 28

Jeff McAffer (jeff@is.s.u-tokyo.ac.jp) wrote:
: In article <1995May4.084315.16971@cvi.ns.nl> jelle@cvi.ns.nl (Jelle Wolthuizen) writes:

:  |Now my question is: what are the possibilities to generate C-code from
:  |VisualWorks code, perhaps with restrictions? I know that some French

: I would really have to question someone who would not accept ST but
: would accept a C program generated by a straight transformation of ST
: to C ala ST/X.  This is like saying "you must deliver in assembler"
: but using C++ and the "output assembler" option on the compiler.
: Great, you've got assembler but it is largely meaningless and
: you still have to keep the original C++ source around for maintenance.

: What is the main motivation for this demand?

Some central IT Staff member has proclaimed as corporate policy that all
programs should be written in C, for _maintainability_ . I agree that this
policy seems silly, but it is the political reality we sometimes have to
live with. The other rationale for wanting C is to minimize the sorts and 
types of technology within a certain, complex system. This reduces system
management efforts. 

<other stuff deleted>
-- 
Jelle Wolthuizen                    voice : +31-30-924901
CVI Traffic & Transport             fax   : +31-30-924235
22, Croeselaan                      e-mail: jelle@cvi.ns.nl
3521 CB  Utrecht
