Legacy INPUT statement in Comet16 vs Comet32

[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Robert G Laurin on October 03, 2017 at 08:19:13:

I just recompile a working program in Comet32 and got an error that shouldn't and was not there. Only change is in a usefile.

I'm pretty sure the previous version was compiled using Comet32...

Looks like the C32 compiler does not like EXCPSUB on a legacy INPUT statement.

If I compile with Comet16, it is fine.

Was there a change in a recent version? I am using Comet 2017.509/17.01

501320 -UCP 00000AE6 CLOSE (PST) ! 501320
501330 -UCP 00000AE9 OPEN (PST) FILEID$,EXCPSUB=EXCPPST ! 501330
501340 -UCP 00000AF4 INPUT (PST) DATA$,EXCPSUB=EXCPPST ! Make sure not Empty ! 501340
501340 -UCP 07 AF4 ****************************** ! Make sure not Empty ! 501340

BTW a wiki search for INPUT returns only the REPORTER INPUT statement. Had to manually get the 'IB Statements/input' page.

Follow Ups:

Post a Followup



What is the name of the main Signature System's Product?  


Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):

Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.

[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]