Searching \ for '[PIC]: JAL v2 released !' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devices.htm?key=pic
Search entire site for: 'JAL v2 released !'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]: JAL v2 released !'
2006\06\17@174036 by Stef Mientki

flavicon
face
 hi all,
finally the new version of JAL is released.
below the press release which contains all the links and other information.
If the message below is unreadable, you can also read the press release
on the next html page
 oase.uci.kun.nl/~mientki/data_www/pic/jal_v2_release.html
On behalf of the beta team,
have fun,
Stef Mientki

*FOR IMMEDIATE RELEASE *

*EASY TO USE JAL EMBEDDED SOFWARE BECOMES EVEN MORE POWERFUL *


The beta team is please to announce the release of JAL version 2.0 (JALv2)


/*JALv2* /is a high-level language for Microchip ^TM  PIC microcontrollers

.

JAL -- *J**ust *A**nother *L**anguage was originally written by Wouter
van Ooijen as a

HLL better suited to PIC architecture yet understandable by new users.
Sharing similarities with PASCAL it has evolved into a solid language
with an enthusiastic user base.


Jalv2 is complete rewrite by Kyle York, author of *PICbsc*_
http://www.casadeyork.com/robot/picbsc/_, building upon this proven core

producing highly optimized code while embracing JAL's simplicity, syntax
and style.


JALv2 now introduces many new powerful features enhancing the already
strong suite, as highlighted below:

*Features:*

   *

     8, 16 and 32 bit words fully supported

   *

     Signed and unsigned word variables

   *

     user definable types

   *

     Automatic BANK handling

   *

     Automatic PAGE handling

   *

     multiple interrupt routines allowed

   *

     Built in support for multiple tables, each up to 255 values long

   *

     Real Bit support OR, XOR, AND, NOT, Set, Test

   *

     arithmetic shift for signed types

   *

     Array functions -- count etc

   *

     highly accurate delay function

   *

     Seamless Inline assembler support

   *

     Supports popular bootloaders

   *

     Enhanced New-User-Friendly Documentation

*Supported Devices:*

   *

     Users have the ability to add any device utilizing the 16F
     architecture

   *

     Initial release 2.0.0 supports 12F-series and 16F-series

*Key Benefits:*

   *

     Convenience: the user can use variables and registers without
     worrying about the intricacies of PIC architecture banks

   *

     Speed: an easy to understand language one can quickly develop
     functional programs

   *

     Power: powerful features simplify programming

   *

     Customization: outputs assembler and hex for unique customization
     situations

   *

     Optimal Code, the compiler optimizes the code to be very tight,
     but keeping it still good readable

*System Requirements:*

Win98, Win2000, WinXP, Linux, freeBSD, MAC

   *

     WINDOWS executable and installer supplied -- see below

   *

     LINUX & FreeBSD - JALv2 is tested on LINUX and FreeBSD, recommend
     the user compile the ANSI C source under their flavour of LINUX or
     FreeBSD.

   *

     MAC - JALv2 is written in ANSI C, - compatible source is provided.


*Pricing & Availability*
FREE - Version 2.0.0 is available immediately


JALv2 windows installer- basic package includes JALedit, manual, libraries:

_http://www.wattystuff.net/jal2pic/downloads/jal_v2_package_very_small.exe
(1.8 MB)
<http://www.wattystuff.net/jal2pic/downloads/jal_v2_package_very_small.exe>_


JALv2 windows installer- full package includes JALedit, manual,
libraries, JALss (simulator), INC2JAL (Microchip ^TM   register
translation):

_http://www.wattystuff.net/jal2pic/downloads/jal_v2_package.exe (5.2 MB)
<http://www.wattystuff.net/jal2pic/downloads/jal_v2_package.exe>_


JALv2 latest release:

_http://www.casadeyork.com/jalv2.zip <http://www.casadeyork.com/jalv2.zip>_


The Source (freeBSD license) is available at:

_http://www.casadeyork.com/jalv2src.zip <http://www.casadeyork.com/jalv2src.zip>_


*Libraries and Documentation*

Basic Examples are included in the Windows distribution and documented

in the new enhanced MANUAL:

_http://www.wattystuff.net/jal2pic/downloads/pjal_doc_html.zip_

_http://www.wattystuff.net/jal2pic/downloads/pjal_doc_pdf_a4.zip_

_http://www.wattystuff.net/jal2pic/downloads/pjal_doc_pdf_letter.zip_

_http://www.wattystuff.net/jal2pic/downloads/pjal_doc_sources.zip_


Stef Mientki's extensive JAL libraries have been updated for JALv2, you
always can find the latest version under the tab JAL-libraries on  

_http://pic.flappie.nl <http://pic.flappie.nl/>_


Demo Programs, including all libraries(already included in the windows
installer)

_http://www.wattystuff.net/jal2pic/downloads/jal_v2_demos.zip (120 kB)
<http://www.wattystuff.net/jal2pic/downloads/jal_v2_demos.zip>_


JAL V2 Migration Document - updating from JAL 0.4xx and additional notes
under the tab JAL-v2 on  

_http://pic.flappie.nl <http://pic.flappie.nl/>_

*Supporting Software*


JALedit A simple but yet complete Editor / IDE, has been updated by
original author Sunish Issac to seamlessly work with JALv2 accommodating
new JAL features and adding user enhancements.

JALeditv2 has been endorsed by the Beta team.

JALeditv2 is available separately:

_http://www.wattystuff.net/tiki/tiki-index.php?page=JALedit_


Textpad- owners of Textpad may wish to use this configuration

_http://www.wattystuff.net/tiki/tiki-index.php?page=TextPad_


ViM editor for linux has been tested with JALv2 by the developers:

_http://www.vim.org/_


INC2JAL TRANSLATION -- a Windows-only tool to translate MPASM registers
to JALv2 is provided:

_http://www.wattystuff.net/jal2pic/downloads/inc2jal.zip (330 kB)
<http://www.wattystuff.net/jal2pic/downloads/inc2jal.zip>_



*For further information:*

* *

Contact and Support via the Yahoo JAL users group:
_http://www.groups.yahoo.com/group/jallist_


Microchip Technology _http://www.microchip.com
<http://www.microchip.com/>_ is the leading 8-bit microcontroller vendor
in units sold and second in overall revenue.
_http://biz.yahoo.com/ibd/060516/general01.html_




Approved by the Beta Team (alphabetically):

Bert van Dam, Sunish Issac, Dave Lagzdin, Javier Martinez

Stef Mientki, Wouter van Ooijen, Michael Reynolds, André Steenveld

Joep Suijs, Vasile Surducan, Michael Watterson, Kyle York


DJL 06/16/2006

--------------- end ---------------------------

2006\06\17@193456 by Jason

flavicon
face
From: "Stef Mientki" <spam_OUTs.mientkiTakeThisOuTspammailbox.kun.nl>
Sent: Saturday, June 17, 2006 2:40 PM

This is very welcome news.  I was still using 0.46, which is feeling very
dated now.

Any idea when support for 18F devices will be available though?

Thanks,
 Jason


2006\06\17@212153 by Xiaofan Chen

face picon face
On 6/18/06, Stef Mientki <.....s.mientkiKILLspamspam@spam@mailbox.kun.nl> wrote:
>   hi all,
> finally the new version of JAL is released.
> below the press release which contains all the links and other information.
> If the message below is unreadable, you can also read the press release
> on the next html page
>   oase.uci.kun.nl/~mientki/data_www/pic/jal_v2_release.html
> On behalf of the beta team,
> have fun,
> Stef Mientki

It seems to me that the configure script for Linux is missing and it will
be a bit difficult to build the Linux binary from the current Makefiles
since quite some of the include files are hard-coded.

mcuee@ubuntu:~/Desktop/build/jalv2/jalv2$ make
make -C libutils
make[1]: Entering directory `/home/mcuee/Desktop/build/jalv2/jalv2/libutils'
make[1]: *** No rule to make target
`/usr/lib/gcc-lib/i486-linux/3.3.5/include/stddef.h', needed by
`mem.o'.  Stop.
make[1]: Leaving directory `/home/mcuee/Desktop/build/jalv2/jalv2/libutils'
make: *** [libutils/libutils.a] Error 2

2006\06\17@213020 by Xiaofan Chen

face picon face
On 6/18/06, Xiaofan Chen <xiaofancspamKILLspamgmail.com> wrote:
> On 6/18/06, Stef Mientki <.....s.mientkiKILLspamspam.....mailbox.kun.nl> wrote:
> >   hi all,
> > finally the new version of JAL is released.
>
> It seems to me that the configure script for Linux is missing and it will
> be a bit difficult to build the Linux binary from the current Makefiles
> since quite some of the include files are hard-coded.
>

If I delete the include files section after the "# DO NOT DELETE"
for the indivisual Makefile, I can build jalv2 without a problem under
Linux. It seems to work as well.

mcuee@ubuntu:~/Desktop/build/jalv2/examples$ ../jalv2/jalv2 stef_12f675.jal
jal 2.0 (compiled Jun 18 2006)
generating p-code
0 errors, 0 warnings
178 tokens, 21034 chars; 625 lines; 3 files
generating PIC code pass 1
generating PIC code pass 2
writing result
Code area: 12 of 1024 used
Data area: 0 of 192 used
Software stack available: 96 bytes
Hardware stack depth 1
mcuee@ubuntu:~/Desktop/build/jalv2/examples$ ls stef_12f675.*
stef_12f675.asm  stef_12f675.hex  stef_12f675.jal

But since the author says that we should not delete them,
there must be some side effects...

Regards,
Xiaofan

2006\06\17@215538 by John Temples

flavicon
face
On Sun, 18 Jun 2006, Xiaofan Chen wrote:

> On 6/18/06, Xiaofan Chen <EraseMExiaofancspam_OUTspamTakeThisOuTgmail.com> wrote:
>> On 6/18/06, Stef Mientki <s.mientkispamspam_OUTmailbox.kun.nl> wrote:
>>> finally the new version of JAL is released.
>>
>> It seems to me that the configure script for Linux is missing and it will
>> be a bit difficult to build the Linux binary from the current Makefiles
>> since quite some of the include files are hard-coded.
>
> If I delete the include files section after the "# DO NOT DELETE"
> for the indivisual Makefile, I can build jalv2 without a problem under
> Linux. It seems to work as well.

> But since the author says that we should not delete them,
> there must be some side effects...

I don't think the author is saying that.  "# DO NOT DELETE" is
inserted by makedepend.  I haven't looked at the makefile in question,
but that comment implies there is a "depend" target, meaning you
simply do "make depend" to update those dependencies.

--
John W. Temples, III

2006\06\17@222147 by Xiaofan Chen

face picon face
On 6/18/06, John Temples <@spam@piclistKILLspamspamxargs.com> wrote:
> > If I delete the include files section after the "# DO NOT DELETE"
> > for the indivisual Makefile, I can build jalv2 without a problem under
> > Linux. It seems to work as well.
>
> > But since the author says that we should not delete them,
> > there must be some side effects...
>
> I don't think the author is saying that.  "# DO NOT DELETE" is
> inserted by makedepend.  I haven't looked at the makefile in question,
> but that comment implies there is a "depend" target, meaning you
> simply do "make depend" to update those dependencies.
>

Thanks. It seems that now the depend

mcuee@ubuntu:~/Desktop/build/jalv2/jalv2$ make depend
make[1]: Entering directory `/home/mcuee/Desktop/build/jalv2/jalv2/libutils'
makedepend  *.c *.h
makedepend: warning:  cache.c (reading /usr/include/string.h, line
33): cannot f ind include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cache.c (reading /usr/include/stdlib.h, line
33): cannot f ind include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cache.c (reading /usr/include/bits/types.h, line
31): cann ot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cache.c (reading /usr/include/sys/types.h, line
147): cann ot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cache.c (reading /usr/include/alloca.h, line
25): cannot f ind include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cache.c (reading /usr/include/stdio.h, line 34):
cannot fi nd include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cache.c (reading /usr/include/_G_config.h, line
14): canno t find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cache.c (reading /usr/include/wchar.h, line 48):
cannot fi nd include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cache.c (reading /usr/include/gconv.h, line 31):
cannot fi nd include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cache.c (reading /usr/include/libio.h, line 53):
cannot fi nd include file "stdarg.h"
       not in /usr/include/stdarg.h
make[1]: Leaving directory `/home/mcuee/Desktop/build/jalv2/jalv2/libutils'
make[1]: Entering directory `/home/mcuee/Desktop/build/jalv2/jalv2/libcore'
makedepend  *.c *.h
makedepend: warning:  cmd_asm.c (reading /usr/include/stdio.h, line
34): cannot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cmd_asm.c (reading /usr/include/bits/types.h,
line 31): ca nnot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cmd_asm.c (reading /usr/include/_G_config.h,
line 14): can not find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cmd_asm.c (reading /usr/include/wchar.h, line
48): cannot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cmd_asm.c (reading /usr/include/gconv.h, line
31): cannot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cmd_asm.c (reading /usr/include/libio.h, line
53): cannot find include file "stdarg.h"
       not in /usr/include/stdarg.h
makedepend: warning:  cmd_asm.c (reading /usr/include/stdlib.h, line
33): cannot  find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cmd_asm.c (reading /usr/include/sys/types.h,
line 147): ca nnot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cmd_asm.c (reading /usr/include/alloca.h, line
25): cannot  find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  cmd_optm.c (reading /usr/include/string.h, line
33): canno t find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  pfile.c, line 12: cannot find include file "stdarg.h"
       not in /usr/include/stdarg.h
make[1]: Leaving directory `/home/mcuee/Desktop/build/jalv2/jalv2/libcore'
make[1]: Entering directory `/home/mcuee/Desktop/build/jalv2/jalv2/libpic12'
makedepend  *.c *.h
makedepend: warning:  pic_brop.c (reading /usr/include/string.h, line
33): canno t find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  pic_brop.c (reading /usr/include/stdio.h, line
34): cannot  find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  pic_brop.c (reading /usr/include/bits/types.h,
line 31): c annot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  pic_brop.c (reading /usr/include/_G_config.h,
line 14): ca nnot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  pic_brop.c (reading /usr/include/wchar.h, line
48): cannot  find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  pic_brop.c (reading /usr/include/gconv.h, line
31): cannot  find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  pic_brop.c (reading /usr/include/libio.h, line
53): cannot  find include file "stdarg.h"
       not in /usr/include/stdarg.h
makedepend: warning:  pic_brop.c (reading /usr/include/stdlib.h, line
33): canno t find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  pic_brop.c (reading /usr/include/sys/types.h,
line 147): c annot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  pic_brop.c (reading /usr/include/alloca.h, line
25): canno t find include file "stddef.h"
       not in /usr/include/stddef.h
make[1]: Leaving directory `/home/mcuee/Desktop/build/jalv2/jalv2/libpic12'
make[1]: Entering directory `/home/mcuee/Desktop/build/jalv2/jalv2/jal'
makedepend  *.c *.h
makedepend: warning:  jal_asm.c (reading /usr/include/stdio.h, line
34): cannot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  jal_asm.c (reading /usr/include/bits/types.h,
line 31): ca nnot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  jal_asm.c (reading /usr/include/_G_config.h,
line 14): can not find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  jal_asm.c (reading /usr/include/wchar.h, line
48): cannot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  jal_asm.c (reading /usr/include/gconv.h, line
31): cannot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  jal_asm.c (reading /usr/include/libio.h, line
53): cannot find include file "stdarg.h"
       not in /usr/include/stdarg.h
makedepend: warning:  jal_asm.c (reading /usr/include/stdlib.h, line
33): cannot  find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  jal_asm.c (reading /usr/include/sys/types.h,
line 147): ca nnot find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  jal_asm.c (reading /usr/include/alloca.h, line
25): cannot  find include file "stddef.h"
       not in /usr/include/stddef.h
makedepend: warning:  jal_blck.c (reading /usr/include/string.h, line
33): canno t find include file "stddef.h"
       not in /usr/include/stddef.h
make[1]: Leaving directory `/home/mcuee/Desktop/build/jalv2/jalv2/jal'
mcuee@ubuntu:~/Desktop/build/jalv2/jalv2$ make
make -C libutils
make[1]: Entering directory `/home/mcuee/Desktop/build/jalv2/jalv2/libutils'
gcc -O2 -Werror -pedantic -Wall -Wshadow -Wcast-qual -Wcast-align -g
-c -o mem.o mem.c
gcc -O2 -Werror -pedantic -Wall -Wshadow -Wcast-qual -Wcast-align -g
-c -o cache.o cache.c
ar -r libutils.a mem.o cache.o
ar: creating libutils.a
make[1]: Leaving directory `/home/mcuee/Desktop/build/jalv2/jalv2/libutils'
make -C libcore
make[1]: Entering directory `/home/mcuee/Desktop/build/jalv2/jalv2/libcore'
gcc -O2 -Werror -pedantic -Wall -Wshadow -Wcast-qual -Wcast-align -g
-c -o tag.o tag.c
gcc -O2 -Werror -pedantic -Wall -Wshadow -Wcast-qual -Wcast-align -g
-c -o vardef.o vardef.c
cc1: warnings being treated as errors
In file included from variable.h:15,
                from vardef.c:12:
vardef.h:74: warning: type qualifiers ignored on function return type
vardef.h:84: warning: type qualifiers ignored on function return type
vardef.c:310: warning: type qualifiers ignored on function return type
vardef.c:413: warning: type qualifiers ignored on function return type
make[1]: *** [vardef.o] Error 1
make[1]: Leaving directory `/home/mcuee/Desktop/build/jalv2/jalv2/libcore'
make: *** [libcore/libcore.a] Error 2

If I remove the -Werror option in CFLAGS, the build process will be okay.

Regards,
Xiaofan

2006\06\17@230146 by Wayne Topa

flavicon
face
Xiaofan Chen(KILLspamxiaofancKILLspamspamgmail.com) is reported to have said:
{Quote hidden}

You are doing better them I am.  I replaced all of the
/usr/lib/gcc-lib/i486-linux/3.3.5/include/stddef.h lines in all of the
makefile with the correct path for Debian Testing.  Errors reported
were
make -C libcore
make[1]: Entering directory `/home/wtopa/DOWNLOADS/JAL2/libcore'
gcc -O2 -Werror -pedantic -Wall -Wshadow -Wcast-qual -Wcast-align -g    -c -o vardef.o vardef.c
cc1: warnings being treated as errors
In file included from variable.h:15,
                from vardef.c:12:
vardef.h:74: warning: type qualifiers ignored on function return type
vardef.h:84: warning: type qualifiers ignored on function return type
vardef.c:310: warning: type qualifiers ignored on function return type
vardef.c:413: warning: type qualifiers ignored on function return type
make[1]: *** [vardef.o] Error 1
make[1]: Leaving directory `/home/wtopa/DOWNLOADS/JAL2/libcore'
make: *** [libcore/libcore.a] Error 2

Also commented all the lines you did but get the same error, as expected.

Would have thought a configure script would have solved most of the above.

Wayne

--
Plug-and-Play is really nice, unfortunately it only works 50% of the time.
To be specific the "Plug" almost always works.            --unknown source
_______________________________________________________

2006\06\17@231335 by Xiaofan Chen

face picon face
On 6/18/06, Wayne Topa <TakeThisOuTlinuxoneEraseMEspamspam_OUTintergate.com> wrote:
> You are doing better them I am.  I replaced all of the
> /usr/lib/gcc-lib/i486-linux/3.3.5/include/stddef.h lines in all of the
> makefile with the correct path for Debian Testing.  Errors reported
> were
> make -C libcore
> make[1]: Entering directory `/home/wtopa/DOWNLOADS/JAL2/libcore'
> gcc -O2 -Werror -pedantic -Wall -Wshadow -Wcast-qual -Wcast-align -g    -c -o vardef.o vardef.c
> cc1: warnings being treated as errors

The correct procedure is to "make depend" as per the suggest on
by John. Then remove the "-Werror" in CFLAGS of the top Makefile.
Then "make" will do the job. There are many warning message
regarding the vardef.h file.

Regards,
Xiaofan

2006\06\18@021529 by William Chops Westfield

face picon face

On Jun 17, 2006, at 2:40 PM, Stef Mientki wrote:

> finally the new version of JAL is released.

Hmm.  So this is a release separate from the work going on on the
open source effort at jal.sourceforge.net?  How ... interesting.

BillW

2006\06\18@045022 by Vasile Surducan

face picon face
On 6/18/06, William Chops Westfield <RemoveMEwestfwspamTakeThisOuTmac.com> wrote:
>
> On Jun 17, 2006, at 2:40 PM, Stef Mientki wrote:
>
> > finally the new version of JAL is released.
>
> Hmm.  So this is a release separate from the work going on on the
> open source effort at jal.sourceforge.net?  How ... interesting.

William,

Jal from sourceforge is Wouter's jal0.4 with many improved issues
made in essence by Javier Martinez and a few others. Jal04 is still
there with good and bad things. Clap your hand for Wouter.

JalV2 is a complete different compiler made only for PIC16 series
having as moral author by Stef Mientky (it's his struggle) and the
fortune of meeting Kyle York
(which is the brain behind the compiler).
JalV2 is producing a code much well optimised than Jal04, but like any
new compiler it has some tricks of using it (some of them in
understanding the erros
reported during the compilation)

So do not be upset and say thanks to Stef and Kyle or to Kyle and Stef
if you're using it. I'm happy such people does really exist and I'm
proud I could met them on this virtual world.

greetings,
Vasile

2006\06\18@051018 by Stef Mientki

flavicon
face


William Chops Westfield wrote:
> On Jun 17, 2006, at 2:40 PM, Stef Mientki wrote:
>
>  
>> finally the new version of JAL is released.
>>    
>
> Hmm.  So this is a release separate from the work going on on the
> open source effort at jal.sourceforge.net?  How ... interesting.
>  
I think  this new release means that the old development is dead (if it
wasn't already ;-) .
Maybe we should move the new compiler to sourceforge and replace the old
one ??

Stef Mientki

2006\06\18@052807 by Vasile Surducan

face picon face
On 6/18/06, Stef Mientki <s.mientkiEraseMEspam.....mailbox.kun.nl> wrote:
>
>
> William Chops Westfield wrote:
> > On Jun 17, 2006, at 2:40 PM, Stef Mientki wrote:
> >
> >
> >> finally the new version of JAL is released.
> >>
> >
> > Hmm.  So this is a release separate from the work going on on the
> > open source effort at jal.sourceforge.net?  How ... interesting.
> >
> I think  this new release means that the old development is dead (if it
> wasn't already ;-) .
> Maybe we should move the new compiler to sourceforge and replace the old
> one ??

Why do you have always radical solutions ? Does your children never
told you that? Jal 04 does not ask for feeding at sourceforge...
:)
There is plenty room at sourceforge for as many jal versions will be
built from now on...

greetings,
Vasile

>
> Stef Mientki
>
> -

2006\06\18@064137 by Stef Mientki

flavicon
face

>>>
>>>      
>> I think  this new release means that the old development is dead (if it
>> wasn't already ;-) .
>> Maybe we should move the new compiler to sourceforge and replace the old
>> one ??
>>    
>
> Why do you have always radical solutions ? Does your children never
> told you that? Jal 04 does not ask for feeding at sourceforge...
> :)
>  
hi Vasile,
it was just an idea,
and as said I don't know what the rules in the open source community are,
in these kind of cases (I expect not to happen it often)
And to prevent confusion it might be worth to get 1 standard.

I think you can agree that the devolopment of the old JAL compiler,
will now shrink to 0.1 of what it was ....
... so in absolute sense this means ....

Maybe in the west we can come loose more easy from the past and from the
old things then in the east ;-)

cheers,
Stef

2006\06\18@103255 by Gerhard Fiedler

picon face
Stef Mientki wrote:

>>> Maybe we should move the new compiler to sourceforge and replace the old
>>> one ??
>>
>> Why do you have always radical solutions ?
>

> And to prevent confusion it might be worth to get 1 standard.

I don't work with Jal, but here a few thoughts if you want to publish the
v2 compiler sources for general participation.

- You can create a Jal2 project at Sourceforge. Of course it would be
helpful to link to each other from the project's home page and
documentation. This solution is the simplest and least intrusive for both
projects. Since the teams and codebase seem to be quite distinct, I think
this probably makes most sense.

- You can branch the development of the existing Jal project. The tricky
thing with branching is that it requires some discipline on the part of the
users, for example when filing bug reports. Branching usually only makes
sense when a part of the sources is common and/or merging from one branch
to the other can be expected to be of some help. For two completely
separate code lines, it doesn't make much sense.

- You can archive the older Jal line (so that it continues to be available
for download) and continue with the new Jal line, in the same Sourceforge
project. (This seems to be what you were talking about.) This obviously
only makes sense after the work on the original project has stopped.

- If you are concerned about having a common "Jal Standard" but neither
archiving the older code line nor branching sounds good, you could split
out the language definition (and related sources, like documentation and
parser scripts) into a separate project. This could then be used by both
other projects.


> Maybe in the west we can come loose more easy from the past and from the
> old things then in the east ;-)

Hoo boy... how was that with inches, pounds, gallons and BTUs? :)

Gerhard

2006\06\18@112305 by Stef Mientki

flavicon
face

>  
Gerhard,
thanks for the input,
I'll forward that to the beta team.
>> Maybe in the west we can come loose more easy from the past and from the
>> old things then in the east ;-)
>>    
>
> Hoo boy... how was that with inches, pounds, gallons and BTUs? :)
>  
I meant Europe, and except for the UK,
we never heard of inches, pounds, gallons or BTU's ;-)

Stef

2006\06\18@121552 by Wayne Topa

flavicon
face
Xiaofan Chen(EraseMExiaofancspamgmail.com) is reported to have said:
> On 6/18/06, Wayne Topa <RemoveMElinuxoneEraseMEspamEraseMEintergate.com> wrote:
> > You are doing better them I am.  I replaced all of the
> > /usr/lib/gcc-lib/i486-linux/3.3.5/include/stddef.h lines in all of the
> > makefile with the correct path for Debian Testing.  Errors reported
> > were
> > make -C libcore
> > make[1]: Entering directory `/home/wtopa/DOWNLOADS/JAL2/libcore'
> > gcc -O2 -Werror -pedantic -Wall -Wshadow -Wcast-qual -Wcast-align -g    -c -o vardef.o vardef.c
> > cc1: warnings being treated as errors
>
> The correct procedure is to "make depend" as per the suggest on
> by John. Then remove the "-Werror" in CFLAGS of the top Makefile.
> Then "make" will do the job. There are many warning message
> regarding the vardef.h file.
>

Duh.  Not only did I neglect to read the main Makefile, I missed
John's pointer to the make depend.

It works, of course, now.

Thanks

Wayne

--
Signatures > 4 lines are rude.
_______________________________________________________

2006\06\18@143754 by Gerhard Fiedler

picon face
Stef Mientki wrote:

>>> Maybe in the west we can come loose more easy from the past and from the
>>> old things then in the east ;-)
>>
>> Hoo boy... how was that with inches, pounds, gallons and BTUs? :)
>>  
> I meant Europe,

Yes, I later realized your .nl email domain and figured you meant a
different "west" :)

> and except for the UK, we never heard of inches, pounds, gallons or BTU's
> ;-)

Actually, in Germany for example the pound ("Pfund") is still alive and
well. It has been (re)defined to be 500 g though, and therefore is better
integrated than other versions of the pound :)

And up to a few decades ago, the inch ("Zoll") was well known and used. I
would be surprised if other parts of Europe didn't have their share of
"customary units" up until the 1950ies or even later.

Gerhard

2006\06\18@150555 by Stef Mientki

flavicon
face

> Actually, in Germany for example the pound ("Pfund") is still alive and
> well. It has been (re)defined to be 500 g though, and therefore is better
> integrated than other versions of the pound :)
>
>  
I've to admit that here in the Netherlands we also still use "pond" =
500 grams,
and even "ons"=100 grams,
not to speak of physicians  who still use  mmHg,
while there isn't any Mercury  in the hospital ;-)

Stef

2006\06\18@174926 by Daniel Serpell

picon face
part 1 901 bytes content-type:text/plain; charset=ISO-8859-1; format=flowed (decoded 7bit)

Hi!

On 6/17/06, Stef Mientki <RemoveMEs.mientkispam_OUTspamKILLspammailbox.kun.nl> wrote:
>   hi all,
> finally the new version of JAL is released.

Thanks for your work.

Here are two patches to your sources:

- remove-bad-consts.patch
 This removes four "const" keywords misplaced, newer GCC's warn
 about that so the compilation does not succeed.
 Problem is, you can not return a const value, because you always
 return a copy of the object. You can return pointers to const.

- remove-deps.patch
 This removes all the dependencies from the makefiles, so the source
 compiles at the first try. The dependencies are only needed at developing,
 to keep track of the changes on multiple source files, but on release,
 they add more harm.

The patches are relative to the source directory, so they apply with
"patch -p0 < file.patch"

    Daniel.


part 2 8070 bytes content-type:application/zip; name=jalpatches.zip (decode)

part 3 35 bytes content-type:text/plain; charset="us-ascii"
(decoded 7bit)

2006\06\18@175036 by William Chops Westfield

face picon face

On Jun 18, 2006, at 1:50 AM, Vasile Surducan wrote:

>> Hmm.  So this is a release separate from the work going on on the
>> open source effort at jal.sourceforge.net?  How ... interesting.
>

> JalV2 is a complete different compiler

So is JalV2 based originally on Wouter's source, or just the externally
visible implementation?  Just curious.  I don't think it makes a real
difference...

> So do not be upset...

I'm not upset; just amused.  Polyfurcation is a necessary consequence of
open source, I guess...

> Supported Devices:
>
>     * Users have the ability to add any device utilizing
>       the 16F architecture
>     * Initial release 2.0.0 supports 12F-series and 16F-series
>
This does mean all chips with both 12 and 14 bit instruction words,
right?
(I looked at the page, I looked at the docs, this wasn't quite clear...)

BillW

2006\06\18@191716 by olin piclist

face picon face
Gerhard Fiedler wrote:
> And up to a few decades ago, the inch ("Zoll") was well known and used.

Really?  My grandfather who was born in 1898 and lived in Berlin until 1945
always used centimeters and I got the impression that was normal business.


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products

2006\06\18@193851 by Stef Mientki

flavicon
face


William Chops Westfield wrote:
> On Jun 18, 2006, at 1:50 AM, Vasile Surducan wrote:
>
>  
>>> Hmm.  So this is a release separate from the work going on on the
>>> open source effort at jal.sourceforge.net?  How ... interesting.
>>>      
>
>  
>> JalV2 is a complete different compiler
>>    
>
> So is JalV2 based originally on Wouter's source,
no, it's completly rewritten
>  or just the externally
> visible implementation?  Just curious.  I don't think it makes a real
> difference...
>  
it does make a great difference  ...
the orginal source written by Wouter was started as a simple tool for 16F84,
without bying written as now adays compilers are build, separate
front-end / back-end
(btw, if have no idea what I'm talking about ;-)
The great work of  Wouter was in the definition of the language,
taken over a lot of Pascal, but added a number of specific PIC issues.
The new compiler is written with a separate fornt-end and back-end,
so it shouldn't be difficult to transport it either to another language
or to another processor (at least that's what's told me)
{Quote hidden}

All 14-bit instructions are supported,
12F devices are in fact 16F devices in a small housing,
so for the moment only all 12F and all 16F parts are supported.

cheers,
Stef
> BillW
>
>  

2006\06\18@204708 by Xiaofan Chen

face picon face
On 6/19/06, Stef Mientki <RemoveMEs.mientkiTakeThisOuTspamspammailbox.kun.nl> wrote:
>> > This does mean all chips with both 12 and 14 bit instruction words,
> > right?
> >
> All 14-bit instructions are supported,
> 12F devices are in fact 16F devices in a small housing,
> so for the moment only all 12F and all 16F parts are supported.
>

There are two types of 12F PICs. One type is the baseline (PIC12) PICs
like 12F508/509/510. The other type is the midrange (PIC14) PICs like
12F629/675/635/683/... So I think only the PIC14 PICs are supported
by JAL V2 now.

2006\06\18@205211 by Gerhard Fiedler

picon face
Olin Lathrop wrote:

> Gerhard Fiedler wrote:
>> And up to a few decades ago, the inch ("Zoll") was well known and used.
>
> Really?  My grandfather who was born in 1898 and lived in Berlin until
> 1945 always used centimeters and I got the impression that was normal
> business.

I don't have any "hard" sources for this; it's more my impression (and I'm
talking about a time I don't have any first-hand experience with :)

I think you are right that at that time, meter and centimeter was already
widely used and probably generally known. But I know that both my father
and my grandfather knew what a Zoll is, not theoretically, but from
practical use. I also know that when I was young (in the 60ies), the word
"Zollstock" could still be heard quite frequently, whereas since about the
80ies it's only used by some real oldtimers and nowadays probably not at
all. The newer synonym is "Meterstab":
http://de.wikipedia.org/wiki/Meterstab. I interpret that as a result that
was caused by the Zoll going out of fashion not too long before.

This page about the Meterstab also states that while the meter was the
legal unit for length in Prussia since 1872 (note that then-Prussia is not
quite identical with now-Germany), a law from 1935 in Germany allowed a
second unit on calibrated instruments, which often was the Zoll. It seems
that various trades still actively used it at that time. They list in the
article woodworking, but I know that plumbers also used Zoll a lot. That's
where my father's working knowledge came from.

Gerhard

2006\06\19@020057 by Wouter van Ooijen

face picon face
> So is JalV2 based originally on Wouter's source, or just the
> externally visible implementation?

Based on the language description, sometimes with the actual or desired
behaviour of the old compiler to fill in some gaps.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu


2006\06\19@020257 by Wouter van Ooijen

face picon face
> All 14-bit instructions are supported,
> 12F devices are in fact 16F devices in a small housing,
> so for the moment only all 12F and all 16F parts are supported.

Microchip got you there: 12F's are 8-pin chips, either 14-bit (12F629)
or 12-bit (12F509) core.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu


2006\06\19@031148 by Goran Hosinsky

picon face
In Sweden a hard meter measure, consisting of pieces about 20 cm long
which you double up, is still called "tumstock", same as German Zollstock.

Gerhard Fiedler wrote:
{Quote hidden}

2006\06\19@052153 by Jan-Erik Soderholm

face picon face
Gerhard Fiedler wrote :

> They list in the article woodworking,...

In Sweden all woodwork are sold in "inch-sizes", even if it's
called "45x95 mm" (= 2"x4"), "45x120mm" (=2"x5") and so on.

And everyone just calles them "twoinchfour" and "twoinchfive"... :-)

Jan-Erik.



2006\06\19@084712 by Howard Winter

face
flavicon
picon face
On Sun, 18 Jun 2006 21:05:44 +0200, Stef Mientki wrote:

>...  
> I've to admit that here in the Netherlands we also still use "pond" =
> 500 grams,
> and even "ons"=100 grams,
> not to speak of physicians  who still use  mmHg,
> while there isn't any Mercury  in the hospital ;-)

I believe US aircraft still set their altimeters in inches of Mercury - even though carrying mercury in
commercial aircraft is illegal! :-)  We use millibars, although the standard is now to call them hectopascals
(same unit, different name, like cycles/s and Hz).  What was the abbreviation for cycles per second,
incidentally?

Cheers,


Howard Winter
St.Albans, England


2006\06\19@090125 by Howard Winter

face
flavicon
picon face
Goran,

On Mon, 19 Jun 2006 08:11:48 +0100, Goran Hosinsky wrote:

> In Sweden a hard meter measure, consisting of pieces about 20 cm long
> which you double up, is still called "tumstock", same as German Zollstock.

So you mean something like this: http://www.tool-up.co.uk/tooldev/images/items/24087.jpg ?

We call this a folding- or carpenter's rule.

Cheers,


Howard Winter
St.Albans, England


2006\06\19@090351 by Stef Mientki

flavicon
face


Howard Winter wrote:

{Quote hidden}

simply c perhaps ????
While MHz = Mc ==>  .... ;-)
Stef

>Cheers,
>
>
>Howard Winter
>St.Albans, England
>
>
>  
>

2006\06\19@091334 by Jan-Erik Soderholm

face picon face
Howard Winter :

> On Mon, 19 Jun 2006 08:11:48 +0100, Goran Hosinsky wrote:
>
> > In Sweden a hard meter measure, consisting of pieces about
> > 20 cm long  which you double up, is still called "tumstock",
> > same as German Zollstock.
>
> So you mean something like this:
> http://www.tool-up.co.uk/tooldev/images/items/24087.jpg ?

I'm not Göran, but yes, that's right.

Just that in Sweden they have in many cases simply
removed the "non-metric" scale, as in this case :

http://www.jula.se/Butik/assets/product_images/stora/029121_c.jpg

:-)

Jan-Erik.



2006\06\19@095354 by Goran Hosinsky

picon face
Thats the rule I mean, "tumstock"

Howard Winter wrote:
> Goran,
>
> On Mon, 19 Jun 2006 08:11:48 +0100, Goran Hosinsky wrote:
>
>> In Sweden a hard meter measure, consisting of pieces about 20 cm long
>> which you double up, is still called "tumstock", same as German Zollstock.
>
> So you mean something like this: http://www.tool-up.co.uk/tooldev/images/items/24087.jpg ?
>
> We call this a folding- or carpenter's rule.
>
> Cheers,
>
>
> Howard Winter
> St.Albans, England
>
>

More... (looser matching)
- Last day of these posts
- In 2006 , 2007 only
- Today
- New search...