Re: Problems with lposix on win32

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

• Subject: Re: Problems with lposix on win32
• From: Rici Lake <lua@...>
• Date: 2006年1月15日 21:33:50 -0500

---

On 15-Jan-06, at 6:19 PM, D Burgess wrote:

I agree with this.
On 1/16/06, Edgar Toernig <froese@gmx.de> wrote:

PS: I don't like the name osex. I'd simply put them into os.

I agree with this, too. Loading the extended os package should extend the existing os package, not create a new one. Truly platform specific os interfaces could go in separate packages or subpackages (os.macosx)

---

• Follow-Ups:
  • Re: Problems with lposix on win32, Chris Marrin

• References:
  • Problems with lposix on win32, Chris Marrin
  • Re: Problems with lposix on win32, Rici Lake
  • Re: Problems with lposix on win32, D Burgess
  • Re: Problems with lposix on win32, Chris Marrin
  • Re: Problems with lposix on win32, D Burgess
  • Re: Problems with lposix on win32, Chris Marrin
  • Re: Problems with lposix on win32, D Burgess
  • Re: Problems with lposix on win32, Edgar Toernig
  • Re: Problems with lposix on win32, Chris Marrin
  • Re: Problems with lposix on win32, Edgar Toernig
  • Re: Problems with lposix on win32, D Burgess

• Prev by Date: Re: Problems with lposix on win32
• Next by Date: Re: Problems with lposix on win32
• Previous by thread: Re: Problems with lposix on win32
• Next by thread: Re: Problems with lposix on win32
• Index(es):
  • Date
  • Thread