Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.lang.java.programmer
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion some personal rambling on java the lang
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
George Neuner  
View profile  
 More options Oct 24 2010, 5:34 pm
Newsgroups: comp.lang.lisp, comp.lang.java.programmer
From: George Neuner <gneun...@comcast.net>
Date: Sun, 24 Oct 2010 17:34:36 -0400
Local: Sun, Oct 24 2010 5:34 pm
Subject: Re: some personal rambling on java the lang
Print | View thread | Show original | Report this message | Find messages by this author
On Sat, 23 Oct 2010 05:14:50 +0200, p...@informatimago.com (Pascal J.

Bourguignon) wrote:
>> Writing device drivers or network protocol stacks or file format readers
>> and writers: history shows that this can be done perfectly adequately in
>> lisp or Java or Oberon or Ada or whatever (even C++).  Very few of these
>> languages have so little run-time mechanism that bring-up on bare metal is
>> easy enough to be considered trivial.

AFAIHS, C has the smallest bootstrap.  The only things absolutely
*required* are to define the stack limits, set the stack (and maybe
frame) pointer and (if necessary) jump to the application entry point.
Total required code - less than 10 assembly instructions.  

Optionally, if the application requires dynamic allocation[*] then you
must define the location and limit of the heap and initialize the
allocator.   Less than 10 additional instructions.

That's it ... your C application is up and running.

George
[*] Some of C's standard library functions normally use dynamic
allocation, but those troublesome functions can be avoided or replaced
with versions that use static buffers.  The "added-value" of a
commercial embedded development system (vs, e.g., trying to use a free
compiler) is that the commercial runtime library typically will
include static buffered versions of functions that normally allocate
and also will provide a selection of dynamic allocators optimized for
different purposes.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google