RE: [MiNT] Incorporating other calls into the

["Julian Reschke" <reschke@muenster.de>]

> From: owner-mint@fishpool.com [mailto:owner-mint@fishpool.com]On Behalf
> Of Lonny Pursell
> Sent: Friday, June 25, 1999 6:42 PM
> To: reschke
> Cc: MiNT mailing-list
> Subject: RE: [MiNT] Incorporating other calls into the
>
>
> On Fri, 25 Jun 1999 08:59:48 +0200, Julian Reschke wrote:
>
> >
> >> From: owner-mint@fishpool.com [mailto:owner-mint@fishpool.com]On Behalf
> >> Of Lonny Pursell
> >> Sent: Thursday, June 24, 1999 10:32 PM
> >> To: MiNT mailing-list
> >> Subject: [MiNT] Incorporating other calls into the kernal
> >>
> >>
> >> For sometime I've wanted do some mintnet socket coding but since
> >> all of the socketdev stuff is in 'C' I had real troubles.  At
> >> one point I started to port some of it but a few of the calls
> >> are more than I can port, so I gave up.   I've seen some
> >> discussion of moving some socket calls to the kernal?  Could
> >> the socket cails that are more than simple calls to /device/socket
> >> also be moved to the kernal?
> >>
> >> This would open the doors to coders that use pascal, modula, and
> >> asm and so on to make mintnet apps.  I find it ironic that someone
> >> the knows asm like the back of their hand, has exactly the same
> >> problem I have here.
> >>
> >> Keep in mind I don't know linux, what's common amoungst kernals,
> >> or what it would even take to move these calls.  It's just
> >> a suggestion I felt the need to express.  It might be
> >> totally off the wall.  ;-)
> >
> >Please explain the difference in using a new system call (for which you
> >would probably need new bindings) compared to using the existing
> calls on a
> >socket handle...
>
> I'll try, say for example I need to call resolve(), how do I do
> this if I do not use "C"?  I must port the actual code for this
> call to my language correct?  Or toss my language and switch to "C"?
> I can link other libraries but they must be in DRI format, again
> I think this is a problem as itwould  require me to recompile them
> under some other compiler than what is provided with kgmd?

It seems that you want the code of the MiNT net libraries moved into the
kernel. I understand that you don't feel like porting this code to another
language, but of course then the proper solution would be to generate a
library in DR format. That would make much more sense than moving code that
many people don't need into the static kernel.