Search found 5 matches

Go to advanced search

by crayford
08 Apr 2011, 14:04
Forum: General Discussion
Topic: Porting Poco to the big iron
Replies: 5
Views: 2308

Re: Porting Poco to the big iron

That's unfortunate! I had a plan to use a custom char_traits with BasicBufferedStream but that won't cut it because I need to convert from EBCDIC->ASCII and ASCII->EBCDIC. Also some streams are unbuffered. I'm still learning the code so bear with me. The test suites are proving to be invaluable. Tha...
by crayford
06 Apr 2011, 15:52
Forum: General Discussion
Topic: EchoServer issue
Replies: 0
Views: 980

EchoServer issue

When running the samples for my z/OS port EchoServer threw an exception in ~EchoServerHandler->getPeerName due to ::getpeername
failing because the peer socket was closed. In my enviroment that seems like normal behaviour, there is no peer name buffering on the
socket.
by crayford
06 Apr 2011, 13:37
Forum: General Discussion
Topic: Porting Poco to the big iron
Replies: 5
Views: 2308

Re: Porting Poco to the big iron

ok, I've built Poco and I'm currently running through the test suites. I've changed all the parts that I wouldn't compile or need platform implementations: ⋅ Atomics ⋅ Threads ⋅ Semaphores ⋅ Shared Memory ⋅ Sockets Now I'm going to attack EBCDIC. I w...
by crayford
04 Apr 2011, 05:33
Forum: General Discussion
Topic: Porting Poco to the big iron
Replies: 5
Views: 2308

Re: Porting Poco to the big iron

Thanks for the prompt reply! Your suggestions seem like the way to go. When I've finished the port are you interested in taking the changes into your main source tree or do you want me to keep a seperate patch file? I understand the ASCII issues with Net, I ported libcurl a few years ago. The motiva...
by crayford
03 Apr 2011, 08:53
Forum: General Discussion
Topic: Porting Poco to the big iron
Replies: 5
Views: 2308

Porting Poco to the big iron

Greetings! I'm in the process of porting Poco to the mainframe. By that I mean z/OS not z/Linux. It's going quite well but the big issues are ASCII related. I notice that Poco has an ASCII class which is used by tokenizers. This won't do for an EBCDIC platform and nor will hard coded tests for ASCII...

Go to advanced search

cron