1. eu c source no euphoria exe required to build
- Posted by SDPringle Sep 09, 2008
- 1069 views
Build Euphoria from source, without using Euphoria to build it.
You can also get my patch there too.
Surf to: www.euphoria.blogdns.com/
Download euphoria-1150M-source-c.zip. It has my patches already included.
Shawn Pringle
2. ATTN SHAWN: HTTP 403 FORBIDDEN Re: eu c source no euphoria exe required to build
- Posted by jimcbrown (admin) Sep 09, 2008
- 1068 views
This isn't necessary, once somebody commits the pretranslated C source to svn then we will be in alpha and anyone will be able to check out the source code and build with only a C compiler.
There will be bz2balls of the source for download as well.
Build Euphoria from source, without using Euphoria to build it.
You can also get my patch there too.
Surf to: www.euphoria.blogdns.com/
Download euphoria-1150M-source-c.zip. It has my patches already included.
Shawn Pringle
It would help if the links on that page were not all 403.
3. Re: eu c source no euphoria exe required to build
- Posted by DerekParnell (admin) Sep 09, 2008
- 1046 views
What does "The devs are working on the include files rather than the interpreter." mean, Shawn?
4. Re: eu c source no euphoria exe required to build
- Posted by SDPringle Sep 09, 2008
- 1035 views
It means effort was being concentrated on the .e files in include/std rather than the .e files in source/. It was updated. If you saw the message, I don't know how you got 404s for the other files for they are auto-generated by apache. I'll look in to this.
5. Re: eu c source no euphoria exe required to build
- Posted by ryanj Sep 09, 2008
- 1074 views
Build Euphoria from source, without using Euphoria to build it.
You can also get my patch there too.
Surf to: www.euphoria.blogdns.com/
Download euphoria-1150M-source-c.zip. It has my patches already included.
Shawn Pringle
Apparently, links aren't detected properly in the forum. 
So they need to be enclosed in [[]] like this: [[http://www.euphoria.blogdns.com/]].
6. Re: eu c source no euphoria exe required to build
- Posted by mattlewis (admin) Sep 09, 2008
- 1070 views
It means effort was being concentrated on the .e files in include/std rather than the .e files in source/.
I think we understand what you meant, but Derek was questioning why you said it, because it is wrong. Different people have been working on different things. Here are all of the commits since r1100 that have affected something in the source/ directory (current revision is 1150):
r1101 | mattlewis | 2008-08-30 21:32:54 -0400 (Sat, 30 Aug 2008) | 2 lines r1102 | mattlewis | 2008-08-30 22:37:55 -0400 (Sat, 30 Aug 2008) | 2 lines r1104 | mattlewis | 2008-08-31 17:40:15 -0400 (Sun, 31 Aug 2008) | 2 lines r1106 | jeremy_c | 2008-08-31 22:45:41 -0400 (Sun, 31 Aug 2008) | 1 line r1109 | mattlewis | 2008-09-01 06:30:55 -0400 (Mon, 01 Sep 2008) | 2 lines r1110 | mattlewis | 2008-09-01 08:37:36 -0400 (Mon, 01 Sep 2008) | 2 lines r1111 | mattlewis | 2008-09-01 13:02:21 -0400 (Mon, 01 Sep 2008) | 2 lines r1112 | mattlewis | 2008-09-01 15:02:28 -0400 (Mon, 01 Sep 2008) | 3 lines r1113 | derekparnell | 2008-09-01 17:28:58 -0400 (Mon, 01 Sep 2008) | 1 line r1114 | mattlewis | 2008-09-01 17:49:43 -0400 (Mon, 01 Sep 2008) | 4 lines r1118 | mattlewis | 2008-09-02 05:48:22 -0400 (Tue, 02 Sep 2008) | 5 lines r1120 | mattlewis | 2008-09-02 21:26:41 -0400 (Tue, 02 Sep 2008) | 2 lines r1121 | jeremy_c | 2008-09-03 10:06:51 -0400 (Wed, 03 Sep 2008) | 1 line r1122 | jeremy_c | 2008-09-03 10:24:42 -0400 (Wed, 03 Sep 2008) | 1 line r1126 | CChris | 2008-09-05 16:56:52 -0400 (Fri, 05 Sep 2008) | 6 lines r1130 | derekparnell | 2008-09-06 12:15:11 -0400 (Sat, 06 Sep 2008) | 5 lines r1131 | mattlewis | 2008-09-06 14:20:03 -0400 (Sat, 06 Sep 2008) | 2 lines r1132 | derekparnell | 2008-09-07 00:09:36 -0400 (Sun, 07 Sep 2008) | 1 line r1133 | CChris | 2008-09-07 06:57:49 -0400 (Sun, 07 Sep 2008) | 2 lines r1134 | derekparnell | 2008-09-07 09:20:52 -0400 (Sun, 07 Sep 2008) | 2 lines r1136 | jbrown105a | 2008-09-07 15:58:00 -0400 (Sun, 07 Sep 2008) | 1 line r1137 | jbrown105a | 2008-09-07 18:33:35 -0400 (Sun, 07 Sep 2008) | 2 lines r1138 | jbrown105a | 2008-09-07 18:39:39 -0400 (Sun, 07 Sep 2008) | 1 line r1139 | jbrown105a | 2008-09-07 19:20:07 -0400 (Sun, 07 Sep 2008) | 1 line r1140 | jbrown105a | 2008-09-07 23:28:10 -0400 (Sun, 07 Sep 2008) | 1 line r1141 | mattlewis | 2008-09-08 17:30:19 -0400 (Mon, 08 Sep 2008) | 3 lines r1142 | mattlewis | 2008-09-08 17:35:14 -0400 (Mon, 08 Sep 2008) | 2 lines r1143 | jbrown105a | 2008-09-08 17:58:54 -0400 (Mon, 08 Sep 2008) | 1 line r1144 | derekparnell | 2008-09-08 18:34:58 -0400 (Mon, 08 Sep 2008) | 1 line r1145 | jbrown105a | 2008-09-08 19:01:14 -0400 (Mon, 08 Sep 2008) | 1 line r1146 | derekparnell | 2008-09-09 01:22:38 -0400 (Tue, 09 Sep 2008) | 3 lines r1148 | jbrown105a | 2008-09-09 06:05:09 -0400 (Tue, 09 Sep 2008) | 1 line r1149 | jbrown105a | 2008-09-09 06:25:39 -0400 (Tue, 09 Sep 2008) | 1 line
So that's 33 commits out of 50 that dealt with the source directory. Anyway, the segfault was with the translator, not the interpreter. 
And it's been fixed.
Matt
7. Re: eu c source no euphoria exe required to build
- Posted by DerekParnell (admin) Sep 10, 2008
- 1144 views
Apparently, links aren't detected properly in the forum. So they need to be enclosed in [[]] like this: [[http://www.euphoria.blogdns.com/]].
Actually all one needs to do is prefix it with http://
http://www.euphoria.blogdns.com/
Currently creole assumes that something in the form of <WORD>.<WORD>.<WORD> is a url. I could make it smarter if required, but just using a protocol prefix works already.
The recognised protocols are ...
HTTP: FTP: FILE: HTTPS: SVN: GOPHER: IRC: NEWS: NTTP:
8. Re: eu c source no euphoria exe required to build
- Posted by CChris Sep 10, 2008
- 1040 views
It means effort was being concentrated on the .e files in include/std rather than the .e files in source/. It was updated.
I don't think this is true. What is true is:
- The release notes will concentrate in one line inter^preter features og such importance as defaulted parameters aor forward references, and will detail each new library routine name. This is a normal thing for release notes. They do not reflect the amount of design or programming work that went into each item;
- Interpreter features are something everyone will be faced with, while a library file can be easily modified if something is not convenient. As a result of a group development, decisions that are or could be controversial are not taken, or taken after much discussion. A 1-2 person team could go faster in terms of decisions, but with so little programming man/hour available that the result is even slower to come out.
CChris
9. Re: eu c source no euphoria exe required to build
- Posted by CChris Sep 10, 2008
- 1052 views
Another remark concerning the comments on the http://www.euphoria.blogdns.com page.
None of the svn stuff is assumed to be stable, so some revisions are more stable than other. Some revisions do have bugs, but they didn't show up in the context the committer made tests in. Or not on the same platform.
Also, when a change requires extended periods of time - we are not paid 9-to-5 for this -, there may be intermediate commits that are known to be unstable. Normally this is reported in the log messages. If you remain like a week without updating, the next update is going to be painful. And if you update while change is in progress, it is hardly easier to manage. Private versioning would probably remove this issue, but SF doesn't support it, I think. Nifty use of branches may be a partial solution.
So, if you expect something to be (100-epsilon)% reliable, then wait for official releases. If you don't, there are risks with it, and those risks should be assumed.
CChris
