Re: New editor/Integrated Development Environment/compiler

Hi Willem,


> Pascal J. Bourguignon wrote:
> ) So what's missing? The filing part. One thing you can do to ensure a
> ) clear break of mindset is to store the code into a data base instead of
> ) text files. For a start, you could store it in a postgres database.
> ) There's a pg.el on the web, which let you communicate directly to
> ) postgres. You may store each definition in a different row.
>
> NOOOO! Not Uniface again! I can tell you from experience that storing
> code into a database instead of text files is absolutely horrible.
>
> Of course, it looks great at the beginning when you're whipping up code
> and you don't need to worry about file structure or whatever, but when it
> grows bigger you're left with a horrible mess in a proprietary format.


I'm not familiar with the Uniface system, but it would be interesting
to know some specific problems that you experienced. Was structure
navigation an issue? Or the rulesets to generate the source code? Or
some collaboration conflicts?


> And then you want to put the whole thing into some kind of version control
> system, preferrably with multiple staging areas and whatnot, and then
> you're *really* in trouble.


That's what I think the new editor should have collaboration and
revision control at its core level, with edition features on top. My
experience is that communication and collaboration are the biggest
problems in big projects.


> Here's a break of mindset for you: A filesystem is a database, but with the
> added advantages that it's atransparent, and there are loads and loads of
> existing tools that integrate with it, including version control, backup,
> to name but a few.


The fact that the filesystem is a well-stablished development-system
doesn't make me feel less frustrated about the problems that I find when
I develop my applications in it ;). I have to endure it.

Return to the comp.compilers page.
Search the comp.compilers archives again.