Editors for UNIX Post: 20393

5 More Discussions You Might Find Interesting

1. Programming

editors?

Just started out with C and are looking for a good editor in *nix that marks the code with colors. This is maybe a newbie thing to have the C code in colors but i like it and you can almost always se when you are typing wrong. :) Ive heard that emacs should have that option but i havent...

2. UNIX for Dummies Questions & Answers

Mail utilities and editors.

I was wondering what other mail utilities besides 'mutt, unix mail, PINE and elm' are available for unix. Also, what other editors are around besides 'VI, pico, vim and emacs'... I've been searching the net looking for some answers, but nothing much has come up.. thanx!

3. Windows & DOS: Issues & Discussions

GUI Text Editors in WinXP -- what's their problem?

jEdit, Total Edit, EDXOR, all have one thing in common -- whatever they save in what they call "Unix" encoding and line endings inevitably shows up in a CLI text editor like pico or vim having garbage characters somewhere close to the beginning or, though this is more rare, somewhere in the body of...

4. UNIX and Linux Applications

opinions on video editors

What is everyones opinions on these video editors? PiTiVi Avidemux Cinelerra Kdenlive Kino Linux Video Editing: Top Five Linux Video Editors

5. UNIX for Dummies Questions & Answers

UNIX Basics about shell and editors and default settings

Hi all, I have 3-4 years of experience working on unix environment. I am not a beginner, but unix is not my primary skill set. I am very good at awk programming and doing many of my tasks very well, really very weak on basics. I moved to a new job recently and the settings there are driving me...

LEARN ABOUT OSX

end

GET_END(3)						     Library Functions Manual							GET_END(3)

NAME

       get_end, get_etext, get_edata - get values of UNIX link editor defined symbols

SYNOPSIS

       #include <mach-o/getsect.h>

       unsigned long get_end();
       unsigned long get_etext();
       unsigned long get_edata();

DESCRIPTION

       These routines provide a stopgap measure to programs that use the UNIX link-editor defined symbols.  Use of these routines is very strongly
       discouraged.  The problem is that any program that is using UNIX link editor defined symbols (_end, _etext or _edata) is making assumptions
       that the program has the memory layout of a UNIX program.

       This is an incorrect assumption for a program built by the Mach-O link editor.  The reason that these routines are provided is that if very
       minimal assumptions about the layout are used and the default format and memory layout of the Mach-O link editor is used to build the  pro-
       gram,  some things may work by using the values returned by these routines in place of the addresses of their UNIX link-editor defined sym-
       bols.  So use at your own risk, and only if you know what your doing.  Or better yet, convert the program to use the  appropriate  Mach	or
       Mach-O  functions.   If	you  are  trying to allocate memory use vm_allocate(2), if you are trying to find out about your address space use
       vm_region(2) and if you are trying to find out where your program is loaded use the dyld(3) functions.

       The values of the UNIX link-editor defined symbols _etext, _edata and _end are returned by the routines get_etext, get_edata,  and  get_end
       respectively.  In a Mach-O file they have the following values: get_etext returns the first address after the (__TEXT,__text) section, note
       this my or may not be the only section in the __TEXT segment.  get_edata returns the first address after the (__DATA,__data) section,  note
       this  my  or  may not be the last non-zero fill section in the __DATA segment.  get_end returns the first address after the last segment in
       the executable, note a shared library may be loaded at this address.

SEE ALSO

       ld(1), dyld(3)

Apple Computer, Inc.						  April 10, 1998							GET_END(3)