> BSD has curproc, but that is considerably less likely to be > used in "inoccent code" than "current". I mean, "current what?". > It could be anything, current privledges, current process, current > thread, the current time... I see and I assume calling a random collection of data u.something in BSD was even more logical 8) current is a completely rational name. The problem with current on some of our ports right now is that its a #define. That is a trap for the unwary and one day wants fixing. curproc would be incorrect for linux since its the current task, and a task and unix process are not the same thing Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Adaptec AIC7XXX v 6.0.6 BETA Released Justin T. Gibbs
- Re: Adaptec AIC7XXX v 6.0.6 BETA Released Steven N. Hirsch
- Re: Adaptec AIC7XXX v 6.0.6 BETA Released Justin T. Gibbs
- Re: Adaptec AIC7XXX v 6.0.6 BETA Released David S. Miller
- Re: Adaptec AIC7XXX v 6.0.6 BETA Release... Justin T. Gibbs
- Re: Adaptec AIC7XXX v 6.0.6 BETA Re... Alan Cox
- Re: Adaptec AIC7XXX v 6.0.6 BET... Justin T. Gibbs
- Re: Adaptec AIC7XXX v 6.0.6... Martin Dalecki
- Re: Adaptec AIC7XXX v 6.0.6... Justin T. Gibbs
- Re: Adaptec AIC7XXX v 6.0.6... Martin Dalecki
- Re: Adaptec AIC7XXX v 6.0.6... Alan Cox
- Re: Adaptec AIC7XXX v 6.0.6 BETA Re... Gérard Roudier
- Re: Adaptec AIC7XXX v 6.0.6 BETA Released Alan Cox
- Re: Adaptec AIC7XXX v 6.0.6 BETA Release... Justin T. Gibbs
- Re: Adaptec AIC7XXX v 6.0.6 BETA Re... Steven N. Hirsch
- Re: Adaptec AIC7XXX v 6.0.6 BET... Justin T. Gibbs