[Info-vax] About C - Re: VMS port to x86

Toby Thain toby at telegraphics.com.au
Fri May 25 19:46:45 EDT 2012


On 25/05/12 6:16 PM, Neil Rieck wrote:
> On May 25, 3:59 pm, Michael Kraemer<M.Krae... at gsi.de>  wrote:
>> JF Mezei schrieb:
>>
>>> John Reagan wrote:
>>
>>>> ones as BLISS source and turn the BLISS frontend into the translator tool.
>>>> Ensures source compatibility.  Debugging the code would be a PITA.  Or use
>>>> some Perl/translator-tool into C.  Same problems debugging.
>>
>>> Wouldn't it be easier to translate Bliss into Macro32 and then use the
>>> existing macro32 compiler to get to it to the target platform ?
>>
>> Wouldn't it be even easier to have the Bliss compiler
>> (and all other strange stuff)
>> recoded in C, so it would be just another piece of C software
>> which has to be compiled for a VMS build?
>> You could keep your beloved Bliss based utilities
>> but they would no longer be showstoppers for portability.
>>
>>
>>
>>
>>
>>
>>
>>> Pardon my ignorance here, but does Macro32 *compiler* have 64 bit
>>> extensions ?
>
> I am in full agreement. C has replaced macro assemblers almost
> everywhere. My cousin is a C-programmer in a big Canadian insurance
> company. I like to poke him with the odd barbs about C but he always
> has some good come backs. For example, when I told him "most people
> consider C a low level language" he responded with "it is only low
> level until add to includes". I guess that is sort of true with every
> language.

C is low level on account of the facilities it provides (or lacks). 
#include's don't change that. Perhaps he hasn't been exposed to many 
high level languages.

--Toby

>
> NSR
> _______________________________________________
> Info-vax mailing list
> Info-vax at rbnsn.com
> http://rbnsn.com/mailman/listinfo/info-vax_rbnsn.com
>





More information about the Info-vax mailing list