Little occam advice

Hi folks,

I'm having a little problem trying to compile an occam-pi program.  The error I'm getting is "Error 1 in
routine loadmobile - ARRAYITEM for unsupported MOBILE type".  A brief snippet of what I'm trying to do:

DATA TYPE NODE.ID
  MOBILE RECORD
    MOBILE []BYTE name:
    MOBILE []BYTE protocol:
    MOBILE []BYTE address:
    INT64 attr1:
    INT64 attr2:
    INT32 attr3:
:

PROC link.manager(...)
  MOBILE [100]NODE.ID nodes:
  -- ...
  SEQ
    -- ...
    input ? index; node.id
    nodes[index] := node.id -- ******

The compiler doesn't seem to like the starred line - assigning a mobile value to an array.  For mobile channel
ends, not a problem, but mobile data types it just doesn't seem to like it.  Any advice?

Cheers,

Kevin

compiling/linking occam-pi code in windows 7

 I have just downloaded the Transterpreter for both Windows and Mac OSX. I have
been playing with Arduino for quite a time and I wanted to see what OCCAM can
offer as an alternative.

I have got a little problem in compiling occam-pi code in win 7 and not be able
to find any relevant open forum to post my question, I decided to send it here.
My apologies for any inconvenience.

For testing the Arduino module, I used the Arduino UNO board on both Windows 7
and Mac OSX and it works perfectly well.   Then I wrote the following  occam
code to test the Desktop (TVM) and it works without problem on Mac OSX but it
gives an error in Windows 7.

#INCLUDE "course.module"

PROC main (CHAN BYTE scr!)
 SEQ
   out.string("Hello World!*n", 0, scr!)
   scr ! 'B'
   scr ! '*n'
   scr ! '*n'
   SEQ i = 1 FOR 10
     SEQ
       out.int(i, 0, scr!)
       scr ! 'A'
       scr ! '*n'
:

The error I get in Win 7 is the following:

The status of JCSP

As per my previous email, since there seems to be no effort available to
do a JCSP 1.1 release based on RC-5, I have released 1.1-rc5 from the
confines of the Codehaus snapshot repository into the Codehaus main
repository (*).  When the Maven repository next syncs up with the
Codehaus main repository, the jcsp-1.1-rc5 artefact will be out there in
the wild as the main representative of JCSP. 

I just hope the inconsistency between this and the information on
http://www.cs.kent.ac.uk/projects/ofa/jcsp/ won't confuse anyone too
much.

(*) And marked the "maven build" branch off trunk as being rc6-SNAPSHOT.
This branch only exists in the Git mirror at Codehaus of the Subversion
repository at Kent.  At some point there needs to be a merge so that the
Subversion repository at Kent has the Maven build, and the nascent
Gradle build, in the main repository.

--

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder <at> ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@...
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

GroovyCSP

I think it is unacceptable that people have to use the Codehaus snapshot
repository to get JCSP so that they can use GroovyCSP from the GPars
0.10 release that is present in the main Maven repository.  I am
therefore proposing to push out JCSP 1.1-rc5 as a full release so it
gets into the main Maven repository.

Does this seem like a sensible strategy?  Any obvious pitfalls?

--

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder <at> ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@...
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

CSP and Actor Comparison

Releasing JCSP 1.1.0

I am not sure what the official constitution is regarding JCSP and
decision making, but I assume Adam and myself voting for making the
current trunk, which is 1.1-rc5, into the 1.1.0 release, branching it
for a 1.1.x maintenance branch, tagging it 1.1.0, and releasing it,
doesn't constitute a sufficiency for a decision.  I guess I need to get
a bit more pushy so as to get the people who need to say yes to say yes
-- or, of course no, but I hope they say yes.

There is also the issue of how to get the extra material I have in the
Git repository associated with the Maven and Gradle builds into the
Subversion repository so that the master version is indeed master.

Thanks.

--

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder <at> ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@...
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

JCSP development

Hi,

I am not sure of the appropriate protocol hence this email.

GPars is looking to release its 0.10 mid-May, it is entering a beta
cycle now.  This is the first release of GPars that will have GroovyCSP.
GroovyCSP is effectively just a wrapper around JCSP.  Currently we have
JCSP 1.1-RC5 as the version in the Maven repository.  I would like to
propose that this be released as 1.1.0 (it is a release candidate and as
far as I know there have been no changes to the codebase since it was
released), a maintenance branch taken to cover the need for bug-fix
releases, and that trunk is renumbered as 1.2.0-SNAPSHOT.   I guess my
question is what is the right way of making this proposal.

Thanks.

--

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder <at> ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@...
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Error with the Transterpreter in the Gumstix

The Correct Script of the Error

Gumstix Buildroot

KRoC release process notes

Hi all,

Further to last week's discussion, I've stuck some initial notes about
the KRoC release process on the Wiki here:

  http://projects.cs.kent.ac.uk/projects/kroc/trac/wiki/NotesForDevelopers

Thanks,

--

-- 
Adam Sampson                                         <http://offog.org/>