At 12:54 PM 1/21/2002 +0000, Simon Glover wrote: > While you're online: now that you've split the io ops into their > own separate file, their documentation isn't going to core_ops.pod > any more. The enclosed patch fixes this by autogenerating io_ops.pod > in the same fashion that core_ops.pod is generated, but I'm not sure > whether this is the right thing to do - do we want every ops lib to have > separate documentation, or should we just keep all of the documentation > in one place, in a single file?
My personal feeling is that this makes sense (seperate pod), since they are sort of an "API" compared to the core ops. I'll see what rest of the guys say first, then probably apply it. As far as IO ops, right now they are implemented as inline ops but eventually they will be replaced by method calls on the IO object and won't show up in the core (except maybe some bootstrap print/printerr/readline, etc.) .. At least this is the way I see it, opinions may vary. -Melvin
