Bob the Hamster | 25 Feb 2005 09:57
Favicon

Testing the new list

Welcome to the OHRRPGCE development discussion list! If you are reading 
this, you must be browsing the archives, 'cause right now I am the only 
subscriber! :)

This list is for discussion about the OHRRPGCE 
http://HamsterRepublic.com/ohrrpgce/

---
Bob the Hamster

Mike Caron | 25 Feb 2005 15:21

Test and Announcement

Testing this to see if this works...

And, I'd also like to announce the OCP, or "OHR Commenting Project". 
Participation in the OCP is easy. If you're in the source, and can 
understand what a block of code does, add a comment to enlighten the 
rest of us! Then, generate a patch. If you were fixing a bug or 
implementing a feature, submit it as usual. Or, if you were working 
specifically on the OCP, send patches to me, and I'll consolidate them 
into single big patches to submit to James.

The goal of the OCP is to make it easier for less experienced or less 
archaic programmers to understand and tweak the source for the OHR (no 
offence James, but GOSUB should be banned from usage). If anyone has any 
questions, feel free to contact me.

--

-- 
Mike Caron
Final Fantasy Q
http://finalfantasyq.com

Bob the Hamster | 25 Feb 2005 15:38
Favicon

Test and Announcement

On Fri, Feb 25, 2005 at 05:20:58PM -0500, Mike Caron wrote:
> And, I'd also like to announce the OCP, or "OHR Commenting Project". 
> Participation in the OCP is easy. If you're in the source, and can 
> understand what a block of code does, add a comment to enlighten the 
> rest of us! Then, generate a patch. If you were fixing a bug or 
> implementing a feature, submit it as usual. Or, if you were working 
> specifically on the OCP, send patches to me, and I'll consolidate them 
> into single big patches to submit to James.

Although that is a great suggestion, be careful! Even comments count 
against the memory limitations of the QuickBasic compiler (only at 
compile-time, not at run time)

That is not to say we shouldn't be adding helpful comments, but just 
remember to make them brief and to the point. If something requires a 
very longwinded explanation, do it with a link to the FAQ (also,  note 
that you can write links to the FAQ as 
http://HamsterRepublic.com/ohrrpgce/wiki.php/Faq+Article+Name so you 
don't have to use ugly "gilgamesh" URL's)

Also, before you embark on a massive overhaul, wait for me to try out 
NeoTA's indentation cleanup script. That will change almost every line 
in the source, and colide with any patch you might be working on.

Also-Also, the OCP would probably go smoother if you do a series of 
smaller patches, rather than trying to give me one giant patch for the 
whole thing. That way it is less likely to colide with any other patches 
anybody else happens to be working on at the moment.

> The goal of the OCP is to make it easier for less experienced or less 
(Continue reading)

Bob the Hamster | 25 Feb 2005 19:36
Favicon

Test and Announcement

On Fri, Feb 25, 2005 at 07:21:39PM -0500, Mike Caron wrote:
>    I didn't mean that I wsa going to make a big patch with all the comments.
>    I meant that if someone submits a patch to me, I'll combine it with any
>    other OCP patches I happen to have (but not submitted), and then submit it
>    together, thus saving you work.

Ah, okay. I follow now.

>    As for your other concerns, they could easily be aleviated if QB had a
>    preprocesser. However, due to a distinct lack of one, I wrote another
>    program that I suspect will prove mighty useful. Enter: STRCOM.exe
>    [...]

Dude!
Sometimes somebody comes up with an idea that is just so simple and 
obvious and brilliant, that I feel stupid for never having thought of it 
myself. That trick will really help with compile-time memory 
limitations. Cool :)

(sudden memory)
Actually, maybe it was the qb.exe editor's memory limitations that 
comments mattered for... I don't remember for sure.

Still, the strcom is a great idea, and I will try it out.

>    On that note, I'm having trouble compiling the OHR on this computer (Win
>    2k). It will compile on two others just fine (Win XP and Win 98). I
>    included compile.out so you can help me. I haven't modified the source or
>    anything here, so I don't know what's up...

(Continue reading)

Bob the Hamster | 25 Feb 2005 20:05
Favicon
Gravatar

basclean.py

I had a chance to check out basclean.py today. I think it is going to 
work great, I will just need to make a few improvements. I want to 
supplement the .startswith() and .endswith() string matching with regex 
matching, so I can catch places where I do dumb stuff like putting a FOR 
NEXT loop entirely on one line, and stuff like that.

I will also add support for ELSE and for SELECT CASE blocks

One step closer to the distant land of non-crappy OHR code ;)

---
Bob the Hamster

Bob the Hamster | 25 Feb 2005 21:26
Favicon

Test and Announcement

On Fri, Feb 25, 2005 at 10:50:25PM -0500, Mike Caron wrote:
>    Argh, I have 615k free, and it still won't work. I suppose it's not
>    critical, it just means that I can't test any development I do on my
>    primary computer. *sigh*

Hmmm... there must be some other problem. That is really odd.

>    On a side note, the version of strcom I sent you was defective. It somehow
>    worked up to and including the point in time where I sent it to you. Then
>    it started being dumb. A new, non-defective version is attached. *sigh*

No worries. Thanks.

Mike Caron | 26 Feb 2005 22:19

QBasic quirks

Hi, a couple (more) questions:

Do you know whether an unused DECLARE statement affects the compiled OBJ 
in any drastic way? I'm refering to size/speed or compilation memory 
usage. If not, it would likely be of use to combine all the DECLARE 
statements into a single include (i.e. declares.bi) to simplify moving 
subs from one module to another for the purposes of reducing overall 
compiler difficulties.

On another note, I have managed to compile the OHR source (almost, 
subs2.bas is too big for my computer, apparently, thus the above point) 
under QB 7.1. I had to tweak a couple lines to avoid conflict with new 
functions in 7.1, most notably dir$, curdir$, and all%. I searched and 
replaced the conflicting variables with similar, but non-conflicting, 
names: dir$ -> sDir$, curdir$ -> sCurdir$, all% -> iAll%. A couple other 
fixes were done to fix problems with varying DECLARE statement, but all 
in all, the code should now compile under 4.5 and 7.1.

I have attached a patch for this, and I recomend that it be applied to 
the main source tree. However, the batch files won't work, since in 7.1, 
qb.exe has been renamed qbx.exe. This could be solved by making a new 
branch for the batch files with QB 7.1 versions. I don't know how to do 
this in Subversion, but I know it's possible.

Ok, I'll stop rambling now.

--

-- 
Mike Caron
Final Fantasy Q
http://finalfantasyq.com
(Continue reading)

David Gowers | 27 Feb 2005 01:44
Picon

Re: QBasic quirks

Is QB 7.1 a windows console app, or a dos app?

If it's a dos app, try running it in dosbox*. This gives me 637k of 
conventional memory free. 

* http://dosbox.sf.net

Whew! i finally got basclean.py working 100%!

--
Neo

Mike Caron | 27 Feb 2005 10:16

Re: QBasic quirks

QB 7.1 was created some 6 years before there was a difference, so it 
most certainly is a real mode app. However, I can't get it to even try 
to compile in DOSBox... Is it just me, or does DOSBox not support 
environment varibles?

Mike Caron
Final Fantasy Q
http://finalfantasyq.com

David Gowers wrote:

>Is QB 7.1 a windows console app, or a dos app?
>
>If it's a dos app, try running it in dosbox*. This gives me 637k of 
>conventional memory free. 
>
>* http://dosbox.sf.net
>
>Whew! i finally got basclean.py working 100%!
>
>
>
>--
>Neo
>
>_______________________________________________
>Ohrrpgce-motherhamster.org mailing list
>Ohrrpgce-motherhamster.org <at> lists.motherhamster.org
>http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
>
(Continue reading)

Simon Bradley | 27 Feb 2005 11:36
Picon

Introduction

Hi,

Just joined the list, and thought I'd say hello. My main interest is
in porting game.exe to another platform (PalmOS), but it's quite a
mammoth task, including porting to C and using quite a few bits of the
OS I've never touched before, so don't expect anything for a hundred
years or so. It wouldn't be fun if it was easy. :-)

I expect I wil need to become very familiar with the code if I am to
pull this off, so if I can help anywhere else I will try. I should
probably try to figure out Subversion at some point, too. I downloaded
the book ages ago.

I seem to have managed to compile everything fine with QB4.5, but my
custom.exe and game.exe are about three times the size of the ones I
downloaded. Is something else done to them after the compile?

Cheers,

Simon


Gmane