1. Documentation error regarding peek4s and peek4u functions
- Posted by jaygade Sep 10, 2009
- 1309 views
The doc for peek4s() says that it returns a number in the range 0 to (2^32)-1 and that peek4u() returns a number from -(2^31) to (2^31)-1. This is opposite.
The final paragraph in the description of each is correct, however, regarding how each function interprets the MSB.
So how does one submit a ticket? Or should I put this in the bug system on SourceForge? I'm still more used to the informality of the forum.
2. Re: Documentation error regarding peek4s and peek4u functions
- Posted by jaygade Sep 10, 2009
- 1342 views
Fixed. And I now see the "tickets" tab at the top of the page.
3. Re: Documentation error regarding peek4s and peek4u functions
- Posted by ne1uno Sep 10, 2009
- 1254 views
Fixed. And I now see the "tickets" tab at the top of the page.
r2766 /tags/4.0b2/include/std/memory.e:
most commits are to the trunk. I could be wrong, is there some reason to want to merge changes back to the trunk later?
4. Re: Documentation error regarding peek4s and peek4u functions
- Posted by jaygade Sep 10, 2009
- 1280 views
Fixed. And I now see the "tickets" tab at the top of the page.
r2766 /tags/4.0b2/include/std/memory.e:
most commits are to the trunk. I could be wrong, is there some reason to want to merge changes back to the trunk later?
Should it be to trunk? Did I mess up?
It's been awhile and I'm still trying to re-remember how to do this stuff properly. I was looking for whatever was current. It's been a few months since I've looked up how to do the svn thing.
Sorry about that.
5. Re: Documentation error regarding peek4s and peek4u functions
- Posted by mattlewis (admin) Sep 10, 2009
- 1349 views
Fixed. And I now see the "tickets" tab at the top of the page.
r2766 /tags/4.0b2/include/std/memory.e:
most commits are to the trunk. I could be wrong, is there some reason to want to merge changes back to the trunk later?
Should it be to trunk? Did I mess up?
It's been awhile and I'm still trying to re-remember how to do this stuff properly. I was looking for whatever was current. It's been a few months since I've looked up how to do the svn thing.
Sorry about that.
Yeah, the trunk is where main development happens. In general, tags are meant to be static. They basically point to some release (in this case, the second beta). Branches are often used to do something that you don't want to affect the trunk at that moment (possibly some dramatic refactoring or new features that would break the trunk for a while), or for backpatching an older revision (like if we found and fixed a bug in 3.1.1 and wanted to release a 3.1.2, we'd create a branch for that).
Matt
6. Re: Documentation error regarding peek4s and peek4u functions
- Posted by jeremy (admin) Sep 10, 2009
- 1228 views
Should it be to trunk? Did I mess up?
<snip>
Sorry about that.
Yeah, the trunk is where main development happens. In general, tags are meant to be static.
You didn't mess anything up, don't worry about it. It was brought up, however, as the tag 4.0b2 is pretty much static, or dead. i.e. it stops there and will never be used again. It's the end of the branch. No code will ever continue on from there. So, your changes committed will never be distributed to anyone else. That's the main problem.
You might have something like this:
r123 -> r124 -> r125 -> r126 -> r127 -> r128 -> r129 -> trunk
\- tag 4.0b2 (r124) \- tag 4.0b3 (r128)
So, those tags are never put back into the mainline trunk, which will eventually become 4.0b3, 4.0rc1 and finally 4.0 final. You need to do:
svn co https://rapideuphoria.svn.sourceforge.net/svnroot/rapideuphoria/trunk
and then work from the trunk directory. You'll need to make your changes again in trunk. However, take note that I changed the file extension from .exu to .ex, as we no longer recommend using .exu for Unix only scripts. They are all .ex, as they are all run with eui.
Jeremy
7. Re: Documentation error regarding peek4s and peek4u functions
- Posted by jaygade Sep 10, 2009
- 1206 views
Should it be to trunk? Did I mess up?
<snip>
Sorry about that.
Yeah, the trunk is where main development happens. In general, tags are meant to be static.
You didn't mess anything up, don't worry about it. It was brought up, however, as the tag 4.0b2 is pretty much static, or dead. i.e. it stops there and will never be used again. It's the end of the branch. No code will ever continue on from there. So, your changes committed will never be distributed to anyone else. That's the main problem.
You might have something like this:
r123 -> r124 -> r125 -> r126 -> r127 -> r128 -> r129 -> trunk
\- tag 4.0b2 (r124) \- tag 4.0b3 (r128)
So, those tags are never put back into the mainline trunk, which will eventually become 4.0b3, 4.0rc1 and finally 4.0 final. You need to do:
svn co https://rapideuphoria.svn.sourceforge.net/svnroot/rapideuphoria/trunk
and then work from the trunk directory. You'll need to make your changes again in trunk. However, take note that I changed the file extension from .exu to .ex, as we no longer recommend using .exu for Unix only scripts. They are all .ex, as they are all run with eui.
Jeremy
Okay, got it. I read all this stuff several months (or a year or two??) ago but I've forgotten it all.
Also, WRT exu vs. ex, I got that. But I noticed that it was set to exu in beta2 which is why I went with that convention. I'll keep that in mind as I go through the rest of it. It looked to me like someone had changed it from ex to exu in the past.
