| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | amigaos4: whitespace only, in amigaos4/ | Jarkko Hietaniemi | 2015-09-16 | 1 | -890/+901 |
| | | | | | | | | | Consistent formatting (and using "Andy Broad" style) for the amigaos4 code: astyle --style=bsd --indent=tab=4 amigaos4/*.[hc] (amigaos patch preparation script automates this) | ||||
| * | amigaos4: implement flock() emulation | Andy Broad | 2015-09-16 | 1 | -0/+86 |
| | | | | | | Beware: not an exact implementation, the locks follow the OS level filehandle not the process. | ||||
| * | amigaos4: move the amigaos exec code under amigaos4 | Andy Broad | 2015-09-16 | 1 | -13/+37 |
| | | | | | | | | | | | | | | | | | | Largely reimplements 839a9f02, 54fa14d7, e8432c63, 40262ff4. The upside is that now doio.c and pp_sys.c have much less AmigaOS specific ifdefs. As a downside, the exec code is now forked (pun only partially accidental.) The earlier story regarding fork+exec, that the AmigaOS creating thread doesn't terminate but instead continues running is both true and false. The more detailed story is that the user-observable behaviour is as with POSIX/UNIX. The thread that created the new "task" (to use the AmigaOS terms) does hang around -- but all it does is to wait for the new task to terminate, and more importantly, it holds on to the resources like filehandles. If the task were to immediately terminate, the resources would be reclaimed by the kernel. | ||||
| * | amigaos4: add amigaos the glue code | Andy Broad | 2015-09-05 | 1 | -0/+1056 |
| amigaos.c: pure amigaos code amigaio.c: bridge code between perl and amigaos | |||||
 |
index : delta/perl.git | |
| github.com: perl/perl5.git |
| summaryrefslogtreecommitdiff |