Half a croissant, on a plate, with a sign in front of it saying '50c'
h a l f b a k e r y
Flaky rehab

idea: add, search, annotate, link, view, overview, recent, by name, random

meta: news, help, about, links, report a problem

account: browse anonymously, or get an account and write.



Code Block Namer

Text Editor's feature to name blocks of code by selecting it, and interactively naming the sections of code with one's own words, which would automatically produce a list of names in a separate window or file, organized structurally identical to the original pieces of code in the program.
  [vote for,

(The feature could be useful for reading computer programs, and analysing other types of texts.)
Inyuki, Oct 24 2010

Halfbakery: Roof Irrigation Cooler Roof_20Irrigation_20Cooler
A nostalgic style of writing an idea in the summary. [Inyuki, Oct 25 2010]


       This comes very close to sourcecode navigation features that are standard in most editor/IDEs. Could you describe in more detail how it differs from current technology?   

       As for "other types of texts," the existing technology's not as good. This is well-recognized, but the solutions aren't great.
mouseposture, Oct 24 2010

       In most IDEs the code is automatically organized into classes, functions, and other procedural units. However, sometimes a block of code consists of several such units, or have several statements within one line.   

       As I imagine, once marked code with Code Block Namer, the code background could also change into different colors indicating that the portions of code have different naming.   

       If there is already such thing done somewhere, I am not yet aware of it.
Inyuki, Oct 24 2010

       Well, it makes sense, but it creates structure peculiar to the editor, and not part of the programming language. Most languages' "procedural units" are not flat, but allow for the sort of nesting you describe, and IDEs can recognize, navigate, and display that structure. The major advantage of named code blocks seems to be that it's lightweight, avoiding the need to obsessively structure code at the outset.   

       I wouldn't use the thing myself: very structured code almost always pays off for me, while quick'n'dirty almost always has meant time spent later, refactoring. This might be appropriate to a different coding style, or to a language very tightly integrated with its editor (maybe C#?). [ ]
mouseposture, Oct 24 2010

       Oddly, this might be helpful in Assembly langiage.   

       Presuming, of course, that anyone else still programs in raw Assembler.
8th of 7, Oct 24 2010

       //else// ?
mouseposture, Oct 24 2010

       Yes. Well, we do.   

       <Stands up>   

       "We are the Borg, and we write programs in assembler"   

       <Sits down>   

       <Waits for other Programmers Anonymous members to respond>
8th of 7, Oct 24 2010

       Well, I've been handed a class to teach that involves microcontrollers... And the language of choice is assembler . So I'll bun anything that sounds like a nice coding tool.
Jinbish, Oct 25 2010

       Why is the idea summary longer than the actual idea?
DrBob, Oct 25 2010

       [DrBob], I felt nostalgic about [kaana] who disappeared for good after writing only one idea in 2001, entirely in the summary.
Inyuki, Oct 25 2010

       's a good answer!
gnomethang, Oct 25 2010

       Yuck, XML.
Spacecoyote, Oct 28 2010


back: main index

business  computer  culture  fashion  food  halfbakery  home  other  product  public  science  sport  vehicle