Thread: Looking for a few people willing to test!

Here is a preview of the c-style comments part, the NoColor is a vector that contains zones that are already in use by a comment or something else so that no other colors are added to it:

Code:

	///////////////////////////////////////////////
	// C-Style Comments ///////////////////////////
	
	/* Comment setup ------------------- */
	const int CommentCSize = Colors[ColorChoices[3]].size();
        /* End setup ----------------------- */
	do
	{
		current = code.find("/*", end);
		if (current != string::npos)
		{   
			// Insert the color for comments
			code.insert(current, Colors[ColorChoices[3]]);
			nz.begin = current;
			
			// Now lets search for the matching pair
		        end = code.find("*/", current + CommentCSize + 3);
		        if (end != string::npos)
			{
				// Insert the closing color tag
				code.insert(end + 2, ColorEnd);
				nz.end = end + ColorEnd.size() + 1;
			}		
			// If there is no end, erase what we have
			// inserted and report a syntax error
			else
			{
				code.erase(current, current + CommentCSize);
				return SYNTAXERROR;
			}
			// If everything works add the current
			// comment zone to the no more color vector
                        NoColor.push_back(nz);   	
		}
	}
	while (current != string::npos);
	
	// End C-Style Comments ///////////////////////
       ////////////////////////////////////////////////

here is a update i made, so far i could onyl find one bug and
its werid as hell bug i gotta work on it, it wont highlight using
or namespace when there is a midline comment,
but it will high light everything else correctly even with
a midline comment. i suppose you can live with this bug
and prolly never know it was there, because not many people
are likly to put a midline comment withing using namespace :/

the following is source colored with the program, then the source
is an attachment.

Code:

#pragma once

#include<iostream>
#include<string>

/* Multi-line comment begins here
   And ends here*/

//bool and char

#ifdef __BORLANDC__
  #error "Borland"
#else if defined(_MSC_VER)
  #error "Microsoft"
#endif

using namespace std;

int main()
{
	char ch;
	int num;
	double dnum;
	string mysentence = "hello /*midline true comment*/ bool world"; //a string
	cout << mysentence << endl;
	cout << "welcome to my world" << end;
	return 0;
}

i suppose once i finish and get the bugs out i will
comment the code.

for less then 3k of code, and just under 115 lines of code
id say its pretty impressive.

Well, in my IDE, a single line comment with a backslash at the end doesn't turn the comment's colour.

Code:

// comment . . . \
int i;

How about this? How does your highlighter fare with it?

Code:

puts("printf(\"Hello, World!\n\");");

[edit]
Or this . . .

Code:

puts("\\\"\\");

[/edit]

here is a new update, should accomedate the changes
dwks mention. p.s. that C, this was written for c++.
im sure it doesnt make much of a different in either case but
i wanted to point that out.

im unloading the application, config, and source
file so those who have bene keeping up can make
sure they are gettign the full of the program
and not commenting on old problems. thansk again.

and as always here what that one program looks like
colorized with the program.

Code:

#pragma once

#include<iostream>
#include<string>

/* Multi-line comment begins here
   And ends here*/

//bool and char

#ifdef __BORLANDC__
  #error "Borland"
#else if defined(_MSC_VER)
  #error "Microsoft"
#endif

using namespace std;

int main()
{
	char ch;
	int num;
	double dnum;
	string mysentence = "hello /*midline true comment*/ bool world"; //a string
	cout << mysentence << endl;
	cout << "welcome to my world" << end;
	return 0;
}

there are a still a few bugs in this, more then there was
in the last one, but hey, i onyl get 10 minut eor so a day to
work on this.

Sorry, I'm mainly a C programmer.

(Finally, someone else who uses .RAR instead of .ZIP.)

How about this?

Code:

/* comment \*/
int i;

I haven't tried the latest app, but just wanted to point out a couple of things you'll want to be sure to properly colorize. Here's how yours colorizes:

Code:

// multi-line single-line comment \
   this is a continuation of the comment

char ch = '\\';
const char *str = "\" \
                   blah";
const char *str2 = "\"", str3 = "\"";
/*/ /*/

But here's how it should:

Code:

// multi-line single-line comment \
   this is a continuation of the comment

char ch = '\\';
const char *str = "\" \
                   blah";
const char *str2 = "\"", str3 = "\"";
/*/ /*/

A single-line comment ending with a backslash makes the next line a comment. You aren't colorizing any single-quote (aka. apostrophe) encapsulated data, and when you do you'll want to be sure you account for escaped quotes and backslashes. When it comes to strings, you are apparently making everything from the first quote to the last quote on the line a string. First, there may be multiple strings on a line, and second, a string literal may span multiple lines. Finally, multi-line comments must start with /* and end with */ but they cannot share the asterisk, so /*/ should not start and end a comment. Even if it did, for some reason the second /*/ on a line doesn't get colorized.

Way to make good progress.