amforth-devel

[Amforth-devel] Major redesign of the repository

[Matthias T. <mt...@we...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Today I've changed the repository structure. There are two new
directories at the top level: appl and lib. The directories blocks and
target within trunk are gone together with the makefile there.

Why these changes? amforth itself is basically useless. It needs
a few information about the environment it will run. I call this
an "appl(ication)". In this directory you can find a collection of
targets: AVR Butterfly, the Evaluation Boards and (new!) thanks to
Alexander Haucks impressive work an application to use a tv with
minimal hardware (2 resistors!).

These applications have all that's needed to build and burn the hex
files: a makefile, speed definition files (the former target/xy.asm)
and some useful forthcode specific for this environment. The build
process includes the amforth source tree like a library. It is up
to the developer to decide which version is be used. trunk
is always the lastest and newest, maybe useless version. release/x.y
is stable in a sense that it is never changed.

The lib directory contains forth code snippets that may be useful
across applications. Currently it contains some definitions for
an ANS system and some other more or less trivial words.

These changes should make life easier, feedback is
welcome!

Matthias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGUDEI9bEHdGEMFjMRAr0jAJ9/GQOL7P8k8LEoxng6hZ7fJH8YWQCdEx2j
MeVL1UZI6P/iL7nCzqT1p3g=
=rLw7
-----END PGP SIGNATURE-----

Re: [Amforth-devel] Major redesign of the repository

[<ha...@hu...>]

2007/5/20, Matthias Trute <mt...@we...>:
> Today I've changed the repository structure. There are two new
> directories at the top level: appl and lib. The directories blocks and
> target within trunk are gone together with the makefile there.

Totally cool!  I have done something similar for my private needs, but
it is way better to have amforth being prepared like this upfront.
Thanks!

Something else:  How do you (as in everyone) handle bitwise I/O with
amforth?  The AVR has the very useful SBI/CBI instructions that can be
used to set and clear individual bits without affecting the state of
the other bits in a port.  The bit number is coded into the
instruction, so I am a bit at loss when it comes to defining a proper
amforth word to do it.  Obviously, having cbi and sbi words ( bit port
-- ) would be just great.  Any ideas?

Thanks,
Hans

Re: [Amforth-devel] Major redesign of the repository

[Matthias T. <mt...@we...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hans,

Hans H=FCbner schrieb:
>=20
> Something else:  How do you (as in everyone) handle bitwise I/O with
> amforth?

see lib/bitnames.frt. Thanks to Michael Kalus who has written the
documentation and made some subtle but very useful improvemnts to
my prior design.

> The AVR has the very useful SBI/CBI instructions that can be
> used to set and clear individual bits without affecting the state of
> the other bits in a port.  The bit number is coded into the
> instruction, so I am a bit at loss when it comes to defining a proper
> amforth word to do it.  Obviously, having cbi and sbi words ( bit port
> -- ) would be just great.  Any ideas?

The sbi/cbi work for the IO address _only_, so they are of very
limited use for a general ATmega design.

Matthias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGUHRG9bEHdGEMFjMRAhzNAKDExllhsWYS+0J0xRvdspkxum6+wwCeKn9G
fZBIimalkTi25Cz2DUypRIc=3D
=3Ddgrx
-----END PGP SIGNATURE-----

Re: [Amforth-devel] Major redesign of the repository

[<ha...@hu...>]

Hi Matthias,

I just tried checking out from trunk, and there is no appl or lib
directory.  Has the URL changed?  I used

2007/5/20, Matthias Trute <mt...@we...>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> Today I've changed the repository structure. There are two new
> directories at the top level: appl and lib. The directories blocks and
> target within trunk are gone together with the makefile there.
>
> Why these changes? amforth itself is basically useless. It needs
> a few information about the environment it will run. I call this
> an "appl(ication)". In this directory you can find a collection of
> targets: AVR Butterfly, the Evaluation Boards and (new!) thanks to
> Alexander Haucks impressive work an application to use a tv with
> minimal hardware (2 resistors!).
>
> These applications have all that's needed to build and burn the hex
> files: a makefile, speed definition files (the former target/xy.asm)
> and some useful forthcode specific for this environment. The build
> process includes the amforth source tree like a library. It is up
> to the developer to decide which version is be used. trunk
> is always the lastest and newest, maybe useless version. release/x.y
> is stable in a sense that it is never changed.
>
> The lib directory contains forth code snippets that may be useful
> across applications. Currently it contains some definitions for
> an ANS system and some other more or less trivial words.
>
> These changes should make life easier, feedback is
> welcome!
>
> Matthias
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGUDEI9bEHdGEMFjMRAr0jAJ9/GQOL7P8k8LEoxng6hZ7fJH8YWQCdEx2j
> MeVL1UZI6P/iL7nCzqT1p3g=
> =rLw7
> -----END PGP SIGNATURE-----
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

Re: [Amforth-devel] Major redesign of the repository

[<ha...@hu...>]

Hi Matthias,

while checking out the repository, I found that you decided to move
appl and lib out of the trunk path.  Is that really what you intended?
 It is certainly your decision, but I would think that it would make
more sense to put appl, lib and amforth under trunk (creating a new
amforth directory and moving everything under trunk there).  That way,
it would be easier to check out the full tree and also it would be
easier to snapshot the lib and appl directories when a release is
made.  With the current layout, this would not be easily possible.

Also, such a revised layout would be more in line what SVN
repositories generally look like, so it would be less suprising to use
for people with SVN experience.

Thanks!
Hans

2007/5/20, Matthias Trute <mt...@we...>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> Today I've changed the repository structure. There are two new
> directories at the top level: appl and lib. The directories blocks and
> target within trunk are gone together with the makefile there.
>
> Why these changes? amforth itself is basically useless. It needs
> a few information about the environment it will run. I call this
> an "appl(ication)". In this directory you can find a collection of
> targets: AVR Butterfly, the Evaluation Boards and (new!) thanks to
> Alexander Haucks impressive work an application to use a tv with
> minimal hardware (2 resistors!).
>
> These applications have all that's needed to build and burn the hex
> files: a makefile, speed definition files (the former target/xy.asm)
> and some useful forthcode specific for this environment. The build
> process includes the amforth source tree like a library. It is up
> to the developer to decide which version is be used. trunk
> is always the lastest and newest, maybe useless version. release/x.y
> is stable in a sense that it is never changed.
>
> The lib directory contains forth code snippets that may be useful
> across applications. Currently it contains some definitions for
> an ANS system and some other more or less trivial words.
>
> These changes should make life easier, feedback is
> welcome!
>
> Matthias
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGUDEI9bEHdGEMFjMRAr0jAJ9/GQOL7P8k8LEoxng6hZ7fJH8YWQCdEx2j
> MeVL1UZI6P/iL7nCzqT1p3g=
> =rLw7
> -----END PGP SIGNATURE-----
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Amforth-devel mailing list
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

Re: [Amforth-devel] Major redesign of the repository

[Matthias T. <mt...@we...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hans,

Hans H=FCbner schrieb:

> while checking out the repository, I found that you decided to move=20
> appl and lib out of the trunk path.  Is that really what you
> intended?

Yes. The reason is that I do not really want the applications be
seen as part of amforth. They may be a source of inspiration.

> That way, it would be easier to check out the full tree and also it
> would be easier to snapshot the lib and appl directories when a
> release is made.

I do not intent to make the applications a part of the amforth
releases. The amforth release should be as clean as possible, the
applications may have different release cycles (if any). So they
may reference specific amforth release.

> Also, such a revised layout would be more in line what SVN=20
> repositories generally look like, so it would be less suprising to
> use for people with SVN experience.

And I have seen a lot of svn repositories without the propagated
trunk/releases/branches structure which work really well. The current
structure is simply my _current_ best idea how the organise the
project. But your feedback is very welcome!

Bye
Matthias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGUHRV9bEHdGEMFjMRAk2sAKCOP7SPysQZn9o8zWixKxZUOmu0lQCfcBvN
MaP0bLdEFYoxkc3PXv9ViX8=3D
=3Dtkn+
-----END PGP SIGNATURE-----