On Mar 19, 3:54 pm, William <[email protected]> wrote: > On Mar 19, 9:35 am, "m...@watty" <[email protected]> wrote: > > > > > **** in 1976 **** > > > We have learnt a lot more and Architectures of some CPUs are > > different. > > > Decent language --> P-Code --> specific Assembler. > > > No C please. > > Well, I do plan to look into GCC front-ends, now that Albert has > pointed me in that direction [ thanks again Albert ]. > > I think we're on the same team here - make JAL more available. And a > little healthy competition is a good thing. Good luck with your JAL3 > idea, but my interests go beyond Cortex or any specific chip and > vendor. > > Perhaps we could share a common machine-readable JAL grammar? I'm > looking at Antlr for that. There is a snapshot of my efforts in Antlr > here in the file section. > > However, I can't resist mentioning that your work in C++ to C > preprocessors must have been later than 1976. Perhaps you meant to > type 1979? :-) > > William
1976 I was doing Fortran as a Student. 1976 the UNIX guys (not me) doing C 1980 I was doing Pascal and Z80 assembler. I got my 1st commercial PCB made then (I still have one) of my 2K ROM, 2K RAM Z80 4MHz 160mmx 100mm Industrial Controller. It had a National RTC chip and NiCd, Z80 CTC, Z80 PIO and intel 8255 I think. 64 DIN edge connector for I/O and a piggy back connector beside EPROM for a RAM/ROM expansion board. 1980s serious computer science people realised the severe flaws of C. Decent Programming languages have unambiguous grammer (C need not apply). Decent languages and OS mean only the compiler writer ever manipulates pointers. 1987 was the heyday of C++ to C preprocessors. No "real" C++ compilers work that way anymore. That is when I was working with C++ preprocessors. 1988 I was implementing Real time Database in C for 8051 in circuit Emulator. http://en.wikipedia.org/wiki/Computer_language Popularity is no measure of Goodness. "The period from the 1960s to the late 1970s brought the development of the major language paradigms now in use, though many aspects were refinements of ideas in the very first Third-generation programming languages: * APL introduced array programming and influenced functional programming.[55] * PL/I (NPL) was designed in the early 1960s to incorporate the best ideas from FORTRAN and COBOL. * In the 1960s, Simula was the first language designed to support object-oriented programming; in the mid-1970s, Smalltalk followed with the first "purely" object-oriented language. * C was developed between 1969 and 1973 as a system programming language, and remains popular.[56] * Prolog, designed in 1972, was the first logic programming language. * In 1978, ML built a polymorphic type system on top of Lisp, pioneering statically typed functional programming languages. Each of these languages spawned an entire family of descendants, and most modern languages count at least one of them in their ancestry. The 1960s and 1970s also saw considerable debate over the merits of structured programming, and whether programming languages should be designed to support it.[57] Edsger Dijkstra, in a famous 1968 letter published in the Communications of the ACM, argued that GOTO statements should be eliminated from all "higher level" programming languages.[58] The 1960s and 1970s also saw expansion of techniques that reduced the footprint of a program as well as improved productivity of the programmer and user. The card deck for an early 4GL was a lot smaller for the same functionality expressed in a 3GL deck." Look up Occam, Modula-2, Ada, Forth, Smalltalk, Oberon and C++ in Wikipedia And http://en.wikipedia.org/wiki/CHILL_programming_language (used more as protocol description as alternative to SDL than as a real programming language. We re-implemented CHiLL as C, Pascal and my own schematic based Dataflow language for Z80 called "Hardcore" based on ideas of Westinghouse "Blockware" in 1985 .. 1987 for C.O. Trunk Protocol converters. Java and C# are the only two decent recent attempts at major new languages and while both avoid some of the C flavoured pitfalls the Designer didn't want in C++ (AT&T wanted backward compatibility, which is the greatest ill of C++), they are flawed. Terrible support for multiprocessor, processes, Realtime processing and verification. Realtime java is a fudge. Try doing an embedded system or programming without mono or .net with C# Ruby, php, python and all the similar are toy languages developed for scripting web servers and are useless for embedded, realtime or reliable systems. They have been developed in an adhoc fashion. Really since the late 1980s progress in quality and correctness of programming has advanced very little. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
