[COMMIT] core.ops split
Brent Dax
and all the copyright stuff should be correct.
Please remember to reassemble any Parrot bytecode files you currently
have.
--Brent Dax <br...@brentdax.com>
Perl and Parrot hacker
"Yeah, and my underwear is flame-retardant--that doesn't mean I'm gonna
set myself on fire to prove it."
Simon Glover
On Tue, 22 Jul 2003, Brent Dax wrote:
> The core.ops split has been committed. Documentation has been fixed up,
> and all the copyright stuff should be correct.
>
> Please remember to reassemble any Parrot bytecode files you currently
> have.
A fresh checkout builds and tests fine here (Linux/x86).
One point - should we update the docs Makefile to spit out documentation
for all of the ops files? At the moment we're only doing this for io.ops
and core.ops (which just got a lot smaller).
Simon
Brent Dax
# A fresh checkout builds and tests fine here (Linux/x86).
I forgot to mention that it tests as well as can be expected on Windows
and Darwin.
# One point - should we update the docs Makefile to spit out
documentation
# for all of the ops files? At the moment we're only doing this for
io.ops
# and core.ops (which just got a lot smaller).
This is probably a good idea.
I'd actually suggest combining them into one file--your_ops.pod or
somesuch--that covered all installed ops files, but the way the
documentation is formatted doesn't really lend itself to that.
Simon Glover
On Tue, 22 Jul 2003, Brent Dax wrote:
> # One point - should we update the docs Makefile to spit out
> documentation
> # for all of the ops files? At the moment we're only doing this for
> io.ops
> # and core.ops (which just got a lot smaller).
>
> This is probably a good idea.
>
OK, I've just created a new ops subdirectory in the docs directory, and
changed the docs makefile so that each *.ops file creates a corresponding
*.pod file in there. Everything works OK for me, but I'd appreciate it
if people using non-Unix systems (or non-GNU make) could check that it
works for them.
Simon