ayardley

1. Update READMEs throughout the Parrot repo:

./ext/nqp-rx/README
./ext/winxed/README
./runtime/parrot/library/PCT/README
./runtime/parrot/include/README
./runtime/parrot/dynext/README
./examples/sdl/minesweeper/README
./examples/sdl/tetris/README
./examples/languages/abc/README

ayardley

Whiteknight,

The *.pods for the binaries will reside in 'docs/binaries/' and the README.pods will, for now, reside in 'docs/readmes/' (I will -- & ++ them into their respective spots throughout the distribution.)  In each directory, I will provide an appropriate example_format in each directory, along with an instructional README.pod.

It will take a couple of days, but I'll get the example_formats and README.pods completed and pushed ASAP.

Alvis

ayardley

NotFound:

I was able to build Guitor under cygwin on my wife's XP (SP3) box, using cygwin's bundled distribution of parrot 3.6.0.  I was, however, unable to execute any of examples because of path-related error.  I got the error message,

"load_bytecode" couldn't find file: 'Guitor.pbc'
current instr.: 'initial_load_bytecode' pc 0 ((file unknown):1629545920)

I tried to execute the examples with variations of the following issued from the 'Guitor' directory:

winxed -L="/[path]/[to]/[Guitor]/[build]/[dir]" ./examples/text.winxed

ayardley

Whiteknight:

I'm pretty sure I suggested this a few weeks back, but just in case: Revise/Re-write the below five articles, using Winxed for the source code examples (as opposed to PIR code examples).  The articles I suggest are,

1. "Exceptions" (see 'http://parrot.github.com/html/docs/user/pir/exceptions.pod.html')

2. "Programming Parrot -- Using objects" (see 'http://parrot.github.com/html/docs/user/pir/objects.pod.html')

3. "Programming Parrot -- PMCs " (see 'http://parrot.github.com/html/docs/user/pir/pmcs.pod.html')

ayardley

NotFound:

Thank you for the correction/information.  

The following command, executed in the 'Guitor' directory,

     winxed -L build/ examples/pizarra.winxed

results in the following error,

ayardley

not_gerd:  The below is what I got when I attempted to 'make'. Please let me know if you need any additional information (or if I need to do/check something to make this work for you).

alvis

----------

Windows Vista Home Premium SP2
AMD Phenom 9150e Quad-Core Processor 1.80 GHz
4.00 GB
64-bit OS

ayardley

# ex: set ro:
# DO NOT EDIT THIS FILE
# Generated by gen::config_pm from config/gen/config_pm/config_lib_pir.in and %PConfig
# This file should be the last thing run during
# the make process, after Parrot is built.

# Copyright (C) 2004-2009, Parrot Foundation.

.include 'datatypes.pasm'
.include 'parrot_version.pir'

ayardley

not_gerd:  Again, if I need to change/edit something, please let me know. (Fwiw, I'm rather unfamiliar with cygwin.)

$ git branch
* gerdr/cygcross64
  master

----------

In file included from ./include/parrot/memory.h:13:0,
                 from ./include/parrot/parrot.h:247,

ayardley

not_gerd: I reinstalled cygwin this weekend and installed *only* the mingw64_-x86_64-* toolchain.  This allowed gerdr/cygcross64 to 'make.'  'make test' stalled out, however, on 't/src/extend_vtable.t ..... 101/137'.

Btw, the problem earlier was, I think, everything defaulted to gcc 4.*, and not gcc 3.4.4 bundled with mingw.

I did *try* to use the -mno-cygwin switch, but, evidently, it's been dropped from gcc 4.*, so ....

Hope this helps. 

ayardley

(1) parrotbug, via Net::GitHub or Pithub, uses the github API to open an issue on the new parrotbug proxy repo;

(2) the parrotbug proxy repo throws an open issue event (it's a hook api);

(3) the parrot repo "catches" -- i'm not exactly certain how this happens yet, but the docs say it can -- this event;

(4) Here I'm uncertain.  That is, i'm not sure what we actually *do* to open the issue on the parrot repo. That is, I'm not sure what the thrown event can kick off on the parrot repo to open an issue, but I'll dig around today and fill in this gap.