Re^4: Program Design Around Threads

[choroba]

Call it Thrum or Funicle. To avoid FAIL messages, just die unless ($Config{usethreads}) in the tests. Use a boilerplate module from CPAN to create all the needed files.

[BrowserUk]

Call it Thrum or Funicle.

No thanks.

To avoid FAIL messages, just die unless ($Config{usethreads}) in the tests.

A dieing test will prevent FAIL messages?

Use a boilerplate module from CPAN

Isn't h2xs easier than renaming all the files as well as editing their contents?

And then there is still the problem of working out which files are actually necessary; and deciding what irrelevant guff to fill them with.

[choroba]

A dieing test will prevent FAIL messages?

I was not accurate. Bail out in tests or die in the Makefile.PL|Build.PL.

Also read CPAN Author Notes.

[BrowserUk]

Bail out in tests ...

How do you "Bail out" without dieing?

or die in the Makefile.PL|Build.PL

Hm. I'd forgotten about that heap of dingos kidneys.

Let's see if I've remembered this correctly. I have to:

1. Navigate my way around 26 nested classes (with 13 dependent packages) in order to:
2. Write a perl script that:
3. Generates a makefile that:
4. Invokes perl plus another nested heap of packages to:
5. issue emulated commands that:
6. copy a single file from one directory to another!

Executable configuration files are like using a cement mixer truck to make a pudding.