Re: Subversion Repository for Euphoria

new topic     » goto parent     » topic index » view thread      » older message » newer message

Matt Lewis wrote:
> Robert Craig wrote:
> > I have now managed to set up a Subversion repository
> > for Euphoria on SourceForge. I imported all of the
> > files in my (extended) C:\Euphoria directory, including the
> > source code, demo programs, standard included files, htx
> > subdirectory etc. so anyone can check out the latest 
> > development version of these files.
> 
> Excellent.  I've got my copy checked out.

Good. I've added you as a developer.
You probably know more about SourceForge and SVN
than I do right now, so don't hesitate to straighten
me out if I make a mistake.

> > If you want to modify the Euphoria package, you should 
> > post a message here so we can all discuss whether 
> > it's a good idea or not. Some things people have
> > already done, like porting to a new platform, 
> > extending the Translator to handle more C compilers, or
> > improving the installation process, are not too controversial,
> > and I would rubber stamp them, as long as they do not
> > cause damage to existing functionality, for instance
> > as long as the new code is properly contained 
> > inside #ifdef's for that platform. I'm hoping those people
> > will check out the relevant source, test their changes,
> > and check in the new source without needing too much
> > assistance from me.
> 
> I think one of the first things we should do is to format the code
> to make it easier to work with.  Rob, you write some really good 
> code, but the indenting and such is inconsistent, and that makes it
> difficult to work with.

Cleaning up the code cosmetically sounds like a good idea,
but when you say the indenting is inconsistent, I wonder
what editor you are using, and if you have the tab stops
set to 4 like I do. I still use ed most of the time, and 
the indents seem to be fairly consistent, though when there
are lots of #ifdef's things can get very messy looking.
Maybe you can post an example of a routine that looks
inconsistent in your editor. (Though don't be surprised if
the indents do not show up properly here.)

Having a few coding standards is a good idea,
though with a diverse group of people they might be hard
to enforce if they are too detailed. They might also
tend to discourage new people from submitting code.

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu