Zorba the Hutt (zorbathut) wrote,
Zorba the Hutt

Idea: Store source code in something much closer to parse tree format, instead of raw text. Convert back and forth on load/save (i.e.: it acts like a text editor and just handles the conversions when you store it on the hard drive.) Reason: So that people with weird indent styles will still write well-indented code when I'm loading it on my editor.

Possible problems: I *like* being able to break my indent style once in a while . . . So, just include a bit of data about how, exactly, my version is formatted. If someone else loads it, it ignores my special-casing.

I think it's a good idea that probably nobody will ever implement. Of course, it'd be fiendishly complex, which is the reason why, and it would get away from the "source is just pure text" thing (because while it would still be text, it'd be more interestingly-encoded text) . . . ah well. It was nice to think about.
  • Post a new comment


    default userpic

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 1 comment