1. SVN2331 INFO.E has illlegal characters in it.
- Posted by bernie Aug 03, 2009
- 877 views
Derek:
info.e Line 202 has bad character in it.
Please check other characters in this I think there is more.
This causes a build failure.
Thanks
2. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by DerekParnell (admin) Aug 03, 2009
- 878 views
Derek:
info.e Line 202 has bad character in it.
Please check other characters in this I think there is more.
This causes a build failure.
Thanks
No, it does not have bad characters in it. The back-quote is on line 202 but that has been a valid character for some time now.
What revision number are you trying to build the system with?
3. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by jeremy (admin) Aug 03, 2009
- 881 views
You need to update to at least 2277, then build after that. `...` and """...""" are multiline strings:
sequence email_message = ` Dear @PERSON_NAME@, You have an outstanding balance on your phone bill of @BALANCE@. You should immediately contact the billing department at 555-3231. Thank You, Your Telephone Company` puts(1, email_message)
"""...""" does the same thing except a different syntax. This is incase you need to use """ or ` intermixed. Also, note, that these strings do not have escape characters. This is because all of the characters are type verbatim, so if you need a TAB, then you hit TAB in the middle of the string.
Jeremy
4. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by bernie Aug 03, 2009
- 869 views
Thanks Derek and Jeremy:
Sorry Derek, your changes are coming too fast for me.
My binaries were not up to date.
PS: Jeremy You need to update your eubin/ directory files.
5. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by jeremy (admin) Aug 03, 2009
- 874 views
PS: Jeremy You need to update your eubin/ directory files.
Wow! I hadn't realized how long it had been since I pushed a Windows copy. I just pushed 2334 which is the latest as of right now.
Thanks for the heads up. Only the Linux builds are automated. Everything else requires me thinking about it 
Jeremy
6. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by euphoric (admin) Aug 03, 2009
- 859 views
Only the Linux builds are automated.
Why is 2335 available for Linux, but not 2334? That happens a lot. Revisions are skipped. Not a big deal, but could be.
7. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by jeremy (admin) Aug 03, 2009
- 925 views
Only the Linux builds are automated.
Why is 2335 available for Linux, but not 2334? That happens a lot. Revisions are skipped. Not a big deal, but could be.
The automation is it checks every 15 minutes for a new build. So, many times we will make several changes and commit in groups, such as "core changes" and then right afterwards "demo changes" or something to that effect. Thus, only the last commit within that 15 minute gray area gets built. It would drive my server crazy building on every commit. Sometimes commits happen frequently enough that it wouldn't even be 1/4 way through compiling one commit when another one took place.
Jeremy
8. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by bernie Aug 03, 2009
- 898 views
I think it would have made more sense to just have
a continuation character then you could use comments.
sequence xyz = " \ This is text \ -- a comment can be used too another line " sequence my_struct = " \ -- I can parse this abc int \ -- even if it has comments. def long \ -- It eliminates the " "& ghi float "
9. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by euphoric (admin) Aug 03, 2009
- 933 views
Sometimes commits happen frequently enough that it wouldn't even be 1/4 way through compiling one commit when another one took place.
LULZ. You could probably get rid of some of the older revisions, don't you think? 
10. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by jimcbrown (admin) Aug 03, 2009
- 889 views
Sometimes commits happen frequently enough that it wouldn't even be 1/4 way through compiling one commit when another one took place.
LULZ. You could probably get rid of some of the older revisions, don't you think?
I feel that the older revisions are an important historical archive.
11. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by euphoric (admin) Aug 03, 2009
- 885 views
Sometimes commits happen frequently enough that it wouldn't even be 1/4 way through compiling one commit when another one took place.
LULZ. You could probably get rid of some of the older revisions, don't you think?
I feel that the older revisions are an important historical archive.
The revisions are and will always be in the SVN archive. I'm just talking about on Eubins.
Or, Jeremy, put the latest versions at the top of the page...?
12. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by jimcbrown (admin) Aug 03, 2009
- 886 views
Sometimes commits happen frequently enough that it wouldn't even be 1/4 way through compiling one commit when another one took place.
LULZ. You could probably get rid of some of the older revisions, don't you think?
I feel that the older revisions are an important historical archive.
The revisions are and will always be in the SVN archive. I'm just talking about on Eubins.
Or, Jeremy, put the latest versions at the top of the page...?
I feel that the older eubins binaries, that represent older svn revisions, are an important historical archive.
I don't have a problem with older versions being moved to a new page, though, as long as they're accessible from somewhere.
13. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by jeremy (admin) Aug 03, 2009
- 914 views
I think it would have made more sense to just have a continuation character then you could use comments.
Normally continuation characters will continue the string with nothing after the continuation character, so for example
sequence email = " \ Hello World, \ \ What are you doing?" puts(1, email)
would print "Hello World,What are you doing?" not
Hello World, What are you doing?
Also, the multi-line strings are also raw strings, meaning there are no escape characters. If you write:
sequence email = `Hello\tWorld` puts(1, email)
You will get exactly that
Hello\tWorld
Thus, it's nice for different operations. If you wish to document a string mid way, we can do that already:
sequence abc = "" & -- header "John Doe had a dog." & -- sentence 1 "Jane Doe had a cat." & -- sentence 2 "John's dog chased Jane's cat all the time"
Jeremy
14. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by bernie Aug 03, 2009
- 870 views
Thus, it's nice for different operations. If you wish to document a string mid way, we can do that already:
sequence abc = "" & -- header "John Doe had a dog." & -- sentence 1 "Jane Doe had a cat." & -- sentence 2 "John's dog chased Jane's cat all the time"
Jeremy
You are missing the point I don't like typing all the " "& when I could just do this and still be able to parse the string. because the SEQUENCE will NOT contain the comments as they will if you use the single qoute. sequence abc = " \ -- header John Doe had a dog.\ -- sentence 1 Jane Doe had a cat.\ -- sentence 2 John's dog chased Jane's cat all the time"
15. Re: SVN2331 INFO.E has illlegal characters in it.
- Posted by jeremy (admin) Aug 03, 2009
- 944 views
You are missing the point I don't like typing all the " "& when I could just do this and still be able to parse the string. because the SEQUENCE will NOT contain the comments as they will if you use the single qoute.
I'm just saying that for the rare occassion you will want to document something in the middle of a string, there is an option to do that. I doubt that it comes up often, needing to document what each line of a string is.
Multi-line strings have become a common place in most modern languages. They come in very handy for a variety of tasks.
Jeremy
