on 07/03/02 19:12, Alexander Oberd=F6rster at oberdoer_at_uni-duesseldorf.de
>> Hiroshi says that he has a driver version that works in "enterprise"
>> mode (meaning to connect to a WAP), but he hasn't writen the user
>> interface for it yet. So this means, the solution to our problems is
>> out there, we just have to wait.
> If it's just the user interface that has to be finished, maybe someone
> could assist him? I would guess that this part should be a lot easier
> than the driver itself.
Not at all! From explanations from Paul Guyot, the interface that is writte=
in NewtonScript resides in one memory area while the driver which is writte=
in C++ resides in the C++ areas, and from what I understood, it's somehow
tricky to try to establish communication between the 2 areas. It's doable,
but I don't think it's that easy...
Laurent Daudelin <http://home.cox.rr.com/nemesys>
Logiciels Nemesys Software mailto:nemesys_at_cox.rr.com
dangling pointer n.: [common] A reference that doesn't actually lead
anywhere (in C and some other languages, a pointer that doesn't actually
point at anything valid). Usually this happens because it formerly pointed
to something that has moved or disappeared. Used as jargon in a
generalization of its techspeak meaning; for example, a local phone number
for a person who has since moved to the other coast is a dangling pointer.
Compare dead link.=20
-- Read the List FAQ/Etiquette: http://www.newtontalk.net/faq.html Read the Newton FAQ: http://www.guns-media.com/mirrors/newton/faq/ This is the NewtonTalk mailing list - http://www.newtontalk.net
This archive was generated by hypermail 2.1.2 : Tue Apr 02 2002 - 14:02:23 EST