[HOME] [NSRG] [インフラ] [fml4] [fml8] [北海道] [おすすめの本] Powered by NetBSD and [nuinui.net] .


Table of Contents
Hook Naming Convension


Hooks are required to resolve complicated problems or for compilcated customization. But there are several problems in implemantation.

One problem is naming convension. $START_HOOK of fml4 is ambiguous. It means the location in process but not clarify where in which process. So, fml8 hook naming convension has role and function in it.


There is no common hook among processes. Each process has each hook. In other words, there is no common hook. You need to define plural hooks for different processes even if the hook is same content.

$distribute_XXX_start_hook = q{ ... };
$YYY_XXX_start_hook = $distribute_XXX_start_hook;

Coding style of hooks are expected not too restrictive since perl beginners may code it. fml8 modules have

use strict;
definition but not effective in evalauating hooks. In evaluating a hook, fml8 evaluate it as
no strict;
to disable the strict check.

Function scope differs among fml4 and fml8. In fml4 all functions are global. Instead in fml8 functions are methods, which is not called anytime anywhere. We should provide hooks when we can see $curproc.

[HOME] [NSRG] [インフラ] [fml4] [fml8] [北海道] [おすすめの本] Powered by NetBSD and [nuinui.net] .
Copyright (C) 1993-2017 Ken'ichi Fukamachi mail:< fukachan at fml.org >