Re: Mixed 64-bit system GerH binaries / BillYscripts

On Tue, Sep 02, 2008 at 09:11:01PM +0200, Ger Hobbelt wrote:
...
> The 'unified' approach would look like this:
> 
> learn (spam.css | ham.css) [message] <learn_spam>
> learn (spam.css | ham.css) [message] <learn_ham>
> 
> and you classify using this - as usual:
> 
> classify (spam.css | ham.css) [message]
...
> 
> Does this clear the fog a bit?

hm, do you mean something with '|' in LEARN?  how <learn_{ham,spam}> has 
to be interpreted? perhaps that may be clearer like:

! learn (one two three ... ) [...] <one common+type-specific_flags>
! learn (one two three ... ) [...] <two common+type-specific_flags>
...

or even simply/equivalently:

! learn (one two three ... ) [...] <1 common+type-specific_flags>
! learn (one two three ... ) [...] <2 common+type-specific_flags>
...

ie the param block takes an _optional_ index, required iff LEARN 
_optionally_ names more than 1 class - meaning that such classifier may 
or may not make use of all named classes.
But I don't like it as a requirement at all - sounds like unified ... mess:
consider Trevor's +60 classes:

! learn (one two three ... sixty) [...] <one flags>
! learn (one two three ... sixty) [...] <two flags>
...
! learn (one two three ... sixty) [...] <sixty flags>

when a LEARN can make use but 1 single class at a time; consider a 128+ 
classes case.

pls KISS:

! learn (one) [...] <common + type-specific flags>

unless LEARN for classifier in use _and_ #classes defined 
can/should/must make use of all _or_ just some of them, naming one and
no index is the way to go IMHO.

-- 
paolo

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/