home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 15 Message
/
15-Message.zip
/
oe991009.zip
/
Pr991008.txt
< prev
next >
Wrap
Text File
|
1999-10-09
|
11KB
|
292 lines
OS/2 Programming (Fidonet)
Saturday, 02-Oct-1999 to Friday, 08-Oct-1999
+----------------------------------------------------------------------------+
From: Harald Pollack 27-Sep-99 08:52:04
To: Ian Moote 02-Oct-99 01:56:15
Subj: Maximum threads.
Am 11. Sep 99 11:41, schrieb Ian Moote (1:2424/224.211)
an HARALD POLLACK:
Servus Ian!
IM> Servus! (I've had more E-Mail from Deutschland in the past
IM> week than I think I've had in my entire life!)
If you believe or not, but my mail was NOT from Deutschland (Germany) it was
from Oesterreich (Austria) :-)
Herzliche Gruesse, Harald
-+- Message created on Monday September, 27 1999 08:53:37 EDT
--- WarpEd/2 1.11α
* Origin: LFP Schwechat [OS/2] (2:310/14.59)
+----------------------------------------------------------------------------+
From: Tom Torfs 02-Oct-99 12:32:00
To: Herbert Rosenau 03-Oct-99 13:31:02
Subj: ... Perl
Herbert Rosenau wrote in a message to Thomas Seeling:
HR> No. The only garanteed is: digits are contigous. So '0' through '9'
HR> can be simple in/decremented. But letters not.
Correct.
HR> But practise thows tha independant of chasets and real computers it
HR> would go. And if you don't mix numbers and letters (like 0x41 for
HR> 'A') and uppercase and lowercase it would be independant of ASCII
HR> or EBCDIC.
No, EBCDIC letters are not contiguous.
The obvious solution I talked about would of course be:
const char lookuptable[] = "ABCDEFGHIJKLMNOPQRSTUVWXYZ";
etc.
greetings,
Tom
tomtorfs@village.uunet.be
--- timEd/2 1.10.y2k+
* Origin: 80X86 BBS 32-15-24.62.32 V.34/V.FC (24h/24h) (2:292/516)
900/525
+----------------------------------------------------------------------------+
From: Vitus Jensen 03-Oct-99 23:41:15
To: all 05-Oct-99 01:48:28
Subj: VAC 3.0 Subsystem Library
Hi all,
I'm implementing some DLLs to allow third party applications to control
machines via serial lines. The DLLs use CRT routines (malloc,free) and are
currently statically linked to their own version of CRTs.
I'm wondering whether those statically linked CRTs are the correct way to do
it or may even cause errors (in fact there is currently a hang situation
reported).
Could someone explain the use of the subsystem library (compile switch /Rn)
and whether it's use would be better in my case. And please remember that I
have a thread hidden inside the DLLs (currently started via _beginthread but
/Rn doesn't support it, DosStartThread plus some magic code required?).
Hoping for enlightenment,
Vitus
--- Sqed/rexx 367:
* Origin: SET RESTARTOBJECTS=DONTRESTARTTHEONETHATCRASHED! (2:2474/424.1)
7102/1
+----------------------------------------------------------------------------+
From: Ian Moote 04-Oct-99 08:00:00
To: HARALD POLLACK 05-Oct-99 01:48:28
Subj: Maximum threads.
HP> Servus Ian!
HP>
HP> IM> Servus! (I've had more E-Mail from Deutschland in the past
HP> IM> week than I think I've had in my entire life!)
HP>
HP> If you believe or not, but my mail was NOT from Deutschland
HP> (Germany) it was from Oesterreich (Austria) :-)
Same thing.
I'm kidding!! I'M KIDDING!!!! [;DDD
Sorry about that Harald. [:) I thought that I had checked but I guess I
was making an assumption.
Take care and TTYL.
---
■■ Those who live by the sword get shot by those who don't.
--- AdeptXBBS v1.11y (FREEWare/2)
* Origin: Moote Pointe (1:2424/224.211)
+----------------------------------------------------------------------------+
From: Will Honea 05-Oct-99 02:15:02
To: Vitus Jensen 05-Oct-99 02:15:02
Subj: VAC 3.0 Subsystem Librar
Vitus Jensen wrote to all on 10-03-1999
VJ> Hi all,
VJ>
VJ> I'm implementing some DLLs to allow third party
VJ> applications to control machines via serial lines. The
VJ> DLLs use CRT routines (malloc,free) and are currently
VJ> statically linked to their own version of CRTs.
VJ> I'm wondering whether those statically linked CRTs are the
VJ> correct way to do it or may even cause errors (in fact
VJ> there is currently a hang situation reported).
Well, static linking is a good way to use LOTS of memory. Since you
are using several DLL's you could save a lot of space by dynamic
linking. I use it in one big app I work on and the RTL (re-named per
IBM rules) is bigger than any of the 'functional DLL's.
VJ> Could someone explain the use of the subsystem library (compile
VJ> switch /Rn) and whether it's use would be better in my case. And
VJ> please remember that I have a thread hidden inside the DLLs
VJ> (currently started via _beginthread but /Rn doesn't support it,
VJ> DosStartThread plus some magic code required?).
I use _beginthread() liberally. Most of my threads deal with comm
links - network and serial - so it only makes sense to spin them off
that way. There are some slicker ways to instantiate the threads but
they all seem to deny me some important tweeking. A couple of the
threads I run will need from 28k to 4 meg for stack/heap and
_beginthread() allows me the flexibility to allocate enough that the
thread can then commit whatever it really needs. BTW, all these
threads are launched from DLL code and use semaphores and a message
queue for control and process-related communications. Just be VERY
careful of where you put your waits and be extra meticulous about
cleanup on thread exit. The biggest trap the programmers I work with
fall into is misuse of shared memory - they just can't seem to clean
up after themselves. I think it's a carryover from using multiple
processes rather than true threads. Just to ease your mind a little,
one comm job that gets done has been known to run over 100 threads in an
iterative challenge-reply communications exchange and I've always been
able to kill the process cleanly at any stage. Also, don't be fooled
by the IOC propaganda - the base API's like _beginthread()\_endthread()
are still quite available.
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Mod Rules Poster 06-Oct-99 22:32:18
To: All 07-Oct-99 07:03:00
Subj: OS2PROG Echo Rules
Rev: Wed 6 Oct 99 21:34
============================================================================
The Official Rules of The FidoNet OS2PROG Echo
The objectives of the OS2PROG echo are:
1. To provide a forum in which messages pertaining to programming
for and under OS/2 can be exchanged. It is for the technical
support of OS/2 programming, not OS/2 programs. Queries about
applications and utility programs should be placed in the
general OS2 echo.
2. To provide technical support for newcomers to programming for OS/2.
The rules under which messages are to be exchanged in this echo are:
0. The preferred language is English, but this is not compulsory. Since
most of the participants will be fluent in English, any problem
reports will receive the widest scrutiny if they are written in
English.
1. Real names only. No pseudonyms, "handles", "monickers" or aliases.
2. Relevance to topic. Posts should pertain to programming and
specifically in the OS/2 environment.
3. Advertising. A maximum of 1 advertisement per month by the
author/publisher of software relevant to the topic of the echo will
be permitted. Other products must NOT be advertised.
4. No flaming or abusive language will be tolerated. Also, excessive
profanity is not permitted. Please remember the sensibilities of
others before you upload that QWK packet.
5. Let the moderator do the moderating. Do not reply to "test" messages
from BBSes that have just joined the echo. Do not reply to off-topic
messages or flames. These will all be dealt with by the moderator.
6. You may post uuencoded, xxencoded or base-64 encoded message only
with the prior approval of the moderator. When asking for approval
please state the approximate size of the message, its content and
usefulness to the other participants of the echo.
7. The OS/2 platform is deemed to be:
Native OS/2, both text and PM;
Virtual DOS Machine (VDM & WIN-OS/2) session.
The only reason to discuss DOS/Windows programs in this echo will
be if those DOS/Winodws programs use features specific to OS/2's
VDM or WIN-OS/2 support. General DOS/Windows programming is off-topic.
8. High ASCII is permitted, except 'FF'X, but low ASCII (below '20'X) is
not permitted beyond the standard CR/LF/etc., characters.
9. Programming languages. All programming languages are considered valid.
People using REXX might consider using the OS2REXX echo instead, as
this contains people with a definite REXX focus who don't poll OS2PROG.
However, all compiler, interpreter and assembler languages that are
being used to program OS/2 are suitable for the posting of sample code
in this echo.
These rules will be revised, amended or appended to as needs arise.
Thanks in advance for your compliance.
David Noon
Moderator, FidoNet OS2PROG echo
* Origin: (1:3634/12)
900/525
+----------------------------------------------------------------------------+
From: Mads Orbesen Troest 05-Oct-99 15:46:04
To: Vitus Jensen 08-Oct-99 15:26:08
Subj: VAC 3.0 Subsystem Library
Why, Hello Vitus...
Replying to a message of Vitus Jensen to all:
VJ> Could someone explain the use of the subsystem library (compile switch
VJ> /Rn) and whether it's use would be better in my case.
As far as I am informed, the Subsystem switch means that /no/
startup/termination code is inserted in the generated code. If you use any
library functions whatsoever, this is probably not a very good switch to
check.
These were the incoherent ramblings of ...
... Mads Orbesen Troest <mads@troest.dk>
--- FleetStreet 1.21+
* Origin: Came from the land of desert sand... (2:238/202.1)
7102/1
+----------------------------------------------------------------------------+
+============================================================================+