1 Apr 2008 01:14
Re: IO Ports
On Fri, Mar 28, 2008 at 3:38 AM, Phil Garcia <phil@...> wrote: > While reviewing the PCI implementation, I noticed that an IO port is > defined as an enum in ADC.X86. Since IO ports are common across all > platforms, does anyone see a problem with moving IO.Port from ADC.X86 > to ADC. The platform implementation would remain in ADC.X86? I would > also change IO.Port enum to IOPort class (with an private uint member > for the port location), and remove IOPortStream and IOPortStream8bit, > since their functionality would be include as methods of the new > IOPort. I think that would be fine, although... it might be better to ship it into the normal SharpOS.Kernel namespace if it isn't actually platform-dependent... it could be used in other non-ADC APIs as well, no? -- -- fury long name: William Lahti handle :: fury freenode :: xfury blog :: http://xfurious.blogspot.com/ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
That way, all the
standard globbing constructs will work everywhere, and if you know the
result is going to be on a certain kind of filesystem, then you can
use the extensions. The interface to use in the filesystem drivers is
non-obvious for sure but it's worth looking into.
> Other uses are likely, just don't come to mind.
How about a metadata FS? Granted, the same could be done with some
virtual directories and special handling but you could do:
/path/to/place/**/[Project:Work]
RSS Feed