GRAPHPAK & GFWORKSHOP

[Brad D Byrne]

I think that I have stopped translated my BAS code and ASM code
because nobody help me, why?

Stephane,
Think about what and how you are asking for.
when you ask a (precise, specific, single) question, you usually get
an answer.

But, sometimes you ask for a general(non-specific) solution to a problem
that you havn't identified, or you just ask someone to solve the problem
for you entirely.

these type of questions wont get answered because They make people who want
to help you, have to work more.

It would be like me asking you to make me a list of all the students in Belgium
and organize them for me.

why should you? thats a lot of work, but mostly, by me generally asking you to
organize them, I have shown that I havn't studied or identified the problem
to begin with...



------------------
Wash DC Area

[Michael Mattias]

I think that I have stopped translated my BAS code and ASM code because nobody help me, why?

1. Because many of us don't give away that which we use to put food on the table.
2. Language barriers.
3. Because what you ask is the equivalent of alchemy, and the world is currently enduring a shortage of alchemists.

The tip about the string and array-handling is help. Keeps you from wasting a lot of time.

The tip about not posting the MASM source is help. Keeps you out of court and jail.



[This message has been edited by Michael Mattias (edited July 05, 2003).]

[Stephane Fonteyne]

Dear programmers

I think that I have stopped translated my BAS code and ASM code
because nobody help me, why?

This is public !

Kind regards
Stephane


------------------

[Karl Lessmann]

.

[This message has been edited by Karl Lessmann (edited July 05, 2003).]

[Michael Mattias]

While I doubt the license permits the posting of the MASM source code for Crescent's tools, converting Crescent libraries is probably not a propitious undertaking....

1. Every single function which uses or returns strings must be changed to work with PB/DOS, as the string engines are totally different.

3. Any code dealing with arrays must also be changed due to differences in the array descriptors and alignment.

Other than that (!) it's "plug and play."

MCM

[Brad D Byrne]

Stephane,

I'm not that good with Masm, just learning, but there are many here that are.
so why not post it, it can't be that big, correct?

Brad

------------------
Wash DC Area

[Stephane Fonteyne]

Dear Brad

I can send you the MASM sources if you can give me some translated
this code into PBDOS modules and give me hints how I can do this

Kind regards
Stephane

------------------

[Brad D Byrne]

"...Have anyone help me and rewritten my assembly MASM code?..."

Stephane, that's kind of dificult, without seeing your MASM code...

Brad



------------------
Wash DC Area

[Stephane Fonteyne]

Dear PBDos Users,

A long time ago I think 15 years I used QuickBASIC PDS 7.1 and
Microsoft QuickBASIC v4.5 with the tools of Cresent Software and
I have plans to converted the sources codes translated in Units but
I don't know how I can rewritten de MASM modules into the Build-in
assembler of PB.

I have a few questions about the different of keywords and passing
parameters:

1. The oposite of COMMON in PBCC en PBDOS ?
2. COMMON SHARED GPDat%() and REDIM SHARED Font$() in PBCC en PBDOS ?
3. COMMON modulename/modulename/
4. The oposite of VARSEG en CODESEG in PBCC and PBDOS ?
5. Can I easy translated MASM code into BASM PB Modules?

Have anyone help me and rewritten my assembly MASM code?

Kind regards


------------------