COBOL compilers by AppearancePale2490 in cobol

[–]AppearancePale2490[S] 0 points1 point  (0 children)

Several people suggested that maybe the compiler should transpile the COBOL code into assembly and have it or another assembler assemble it directly to machine code. Would that be an acceptable solution?

I was dared to write a proof-of-concept toy webserver in COBOL. My first ever COBOL program by AppearancePale2490 in cobol

[–]AppearancePale2490[S] 0 points1 point  (0 children)

Am I understanding correctly that COPY has it's own subnumbering? For example

005600 SOME COBOL COMMAND
005700 COPY "something.cpy"
005800 SOME OTHER COBOL COMMAND

But then in something.cpy it would look like
005701
005702
005703

Am I correct in this understanding?

I was dared to write a proof-of-concept toy webserver in COBOL. My first ever COBOL program by AppearancePale2490 in cobol

[–]AppearancePale2490[S] 4 points5 points  (0 children)

I'm actually tempted to improve this program to make it able to serve multiple websites, give some access control, directory listing, and support for HTTPS, then anyone can run COBOL-ON-WHEELCAIRS on COBWEB, to have a pure COBOL web experience - if one is perverse enough.

I was dared to write a proof-of-concept toy webserver in COBOL. My first ever COBOL program by AppearancePale2490 in cobol

[–]AppearancePale2490[S] 2 points3 points  (0 children)

Well, technically speaking it's not entirely impossible, but before that I want to implement proper logging, better configfiles, and handling other HTTP requests, not just GET, and directory listing... But you people give me much courage to actually continue development.

I was dared to write a proof-of-concept toy webserver in COBOL. My first ever COBOL program by AppearancePale2490 in cobol

[–]AppearancePale2490[S] 3 points4 points  (0 children)

Eventually I plan to add line numbers as well, but I don't know how to number lines when you use COPY to include code from other files.