On 01/06/2011 00:58, Isaac Marino Bavaresco wrote:
> Well, it seems that you agree with me, or did I understand it wrong and
> you are disagreeing?

I agree in a  limited sense.

C rather than Assembler.

I'm not impressed with C on 10F/12F/16F/18F etc. (I've tried 3 compilers=20
and I'm experienced with C)
I can see why Olin uses Assembler.

I'm happy to use JAL on 10F/12F/16F/18F,
I'd use C  for dsPIC, PIC24 and PIC32, though I'd likely use Blackfin=20
and ARMs rather than those with C.

I've done PIC 16F, Z80, 8085, x86, 8051, 6502, 78HC11, SC/MP assembler.=20
No ambition to do any more assembler ever.

I've used C, Forth, Pascal and Modula-2 on Z80. The Modula-2 compiler=20
wins there and I've even reused code on x86 32 bit windows M2, with VB6=20
GUI calling the DLL made in M2. Never did Win16. Used Modula-2, C and=20
C++ for DOS and then VB5, C++ and Modula-2 on Win32, later adding C#,=20
Java and VB6.

On Linux & Windows I've used C, C++, C#, Java. Device Drivers on Linux=20
tend to end up being in C. Embedded applications hosted on OpenWRT Linux=20
as testgear in C++. Small cross platform GUI stuff on Java. On Windows=20
only larger GUI projects I'm weaning myself off VB6 to C#, No point to=20
vb.net  I've looked at Ada and Oberon in the past. I learnt C++  a year=20
before C which may have been unusual in late 1980s

JAL2 is very suited to 10F/12/16/18F but is not suited for PIC32, ARM=20
etc even if the compiler was ported. There would need to be V3 superset=20
of the language.

*Special JAL features*
Fantastic Chip include support
at   allows union like feature declare an array and then AT it at a longwor=
d
strings as arrays without a pointer to byte
no pointers (yes this is a positive feature for this size cpu and=20
realtime reliable apps)
Easy to understand libraries without 1976 legacy madness of some C librarie=
s
get and put keywords on procedures and functions to make device drivers=20
look like arrays or variables.
no need for ; on each statement
C like variable declarations
BASIC like IF, LOOP, CASE  constructs
Dead code elimination. No worries including large library and using one=20
little function
special support for accurate SW delays
Very very efficient optimising compiler creating "p-code" which is=20
compiled to PIC Assembler
Libraries optimised for embedded applications and devices commonly=20
connected to PIC rather than mostly originally for Mini-Computer UNIX as=20
is case with C.






--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.