Syntax errors in old C++ code

The following code is from an old C++ program that worked under old versions of Windows
int FAR PASCAL _export NewFrameNameDlg(HWND hDlg, unsigned message, WORD wParam, LONG lParam)
but now generates syntax errors as follows
Error 1067
error C2061: syntax error : identifier 'NewFrameNameDlg'
Error 1068
error C2059: syntax error : ';'
Error 1069
error C2059: syntax error : 'type'
Any idea why?

This will not work correctly in 32-bit Windows (or 64-bit) The type of wParam *must* be WPARAM, the type of lParam *MUST* be LPARAM, and for a dialog handler the return type should be BOOL. The old _export keyword no longer exists, and is not needed in
Win32. FAR is a macro with an empty body and its appearance in all places can be deleted. The quaint and confusing PASCAL keyword may still work, but it would be better to use the now-correct term CALLBACK. Since this is clearly antique Win16 code, there may
be other problems dealing with size of integers. The types int, long, DWORD, UINT and others all represent 32-bit values. The return type for window handlers must have the return type LRESULT, and for dialog handlers, BOOL. All wParam and lParam types must
be changed as I indicated. Note that for Win16, wParam was 16-bit and lParam 32-bit. For Win32, WPARAM, LPARAM and LRESULT are all 32-bit values, and for Win64 they are 64-bit values. Any place the code casts a pointer to an integer type, the code is inherently
incorrect. You must use types like INT_PTR, UINT_PTR, DWORD_PTR and other _PTR-suffixed types for such casts; in Win32 these are pointer-sized integer types (32-bit) and in Win64 they are pointer-sized integer types (64-bit). Types like int, long, DWORD, etc.
are 32-bit values in both Win32 and Win64. Converting code to run on Win32/64 from Win16 requires great caution, because the programming "standards" that were taught for Win16 did not plan on true platform portability, and programmers were taught
terrible techniques such as declaring wParam as WORD and LPARAM as long. And casting pointers to ints and back. All of these techniques lead to disaster.

Similar Messages

Syntax error while creating tax codes for sales n purchases

Hi all,
While creating the tax codes for sales and purchases, i got the below error:
Report RB13A003 has a syntax error.
What should be done?
Thank you

Hi,
I believe, it's RV13A003 report and not RB13A003... What is the exact error message (or is it a dump)?
Regards,
Eli

1093 Syntax error in Adobe devnet code?

Hi All,
I'm new to AC3 so maybe I'm mistaken... but I've tried to follow the steps in this Adobe AC3 tutorial: http://www.adobe.com/devnet/flash/articles/creating_animation_as3.html
..very closely and I'm getting a 1093 syntax error for the code below. Does anyone have an idea what the problem is..and what the fix would be?
The line in red is the one that is indicated in the error message. (It's a tutorial about making a code snippet for tweening.)
Thanks much!
import fl.transitions.*;
import fl.transitions.easing.*;
* This Tween sample shows a fade-in effect
* by default. Change the prop, to, from, and duration
* values to change the animation. You can add code
* in the event handler functions to respond to animation
* event timing.
function onTweenProgress(event:TweenEvent):void
// do something as the tween progresses...
function onTweenEnd(event:TweenEvent):void
// do something when the tween ends...
var prop:String = “alpha”;
var from:Number = 0;
var to:Number = 1;
var duration:Number = 1;
var tween:Tween = new Tween(rect_mc, alpha, Strong.easeOut, from, to, duration, true);
tween.addEventListener(TweenEvent.MOTION_CHANGE, onTweenProgress);
tween.addEventListener(TweenEvent.MOTION_FINISH, onTweenEnd);

It's the double quotes that your code is using on that line. I am guessing you copied and pasted from somewhere. Try retyping the double quotes using your keyboard

Facing syntax error in this simple code snippet

select case
when to_number (to_char(sysdate,'mm')) < 7
then (to_number(to_char(sysdate,'yyyy')) - 1)
from dual
--while if in block works fine
declare
year number;
begin
year := to_number(to_char(sysdate,'yyyy'));
if (to_number(to_char(sysdate,'mm')) < 7) then
year := year - 1;
end if;
dbms_output.put_line('year = '|| year);
end;

You can have:
-- 1 case expression
-- 1.2 searched case expressions
-- 2 simple case statement
-- 2.1 searched case statement
In your case you need the first one(-- 1 case expression ), because you return an expression.
Indeed a simple case statement let you choose a sequence of PL/SQL statements to execute. This follows another syntax.
It's not always true this statements
In PL/SQL you would use "END CASE". For this reason I can quietly show you that I can even use 'case expression' in PL/SQL, without end case:
DECLARE
    subtype TTempWord is varchar2(20);         -- good notation :-)
    valToCompare constant tTempWord:='test';
    temp tTempWord ;
    temp2 tTempWord ;
    --- start locals-------     ;-)
    procedure Compare_Display -- with no parameters just for this dummy test!
    is
    begin
      dbms_output.put_line('Word to compare:'||valToCompare);
      dbms_output.put_line('temp:'||temp);
      dbms_output.put_line('temp2:'||nvl(temp2,'not assigned'));
      temp2:= case temp when valToCompare then 'identic ' else 'NOT identic' end ; -- I'm not using *'END CASE'*
      dbms_output.put_line('    --- after the assignation --->');
      dbms_output.put_line('temp:'||temp);
      dbms_output.put_line('temp2:'||temp2);
      dbms_output.new_line;dbms_output.new_line;
    end;
    --- end locals-------     ;-)
BEGIN
      temp:='testttt';
      Compare_Display ;
      temp:=valToCompare;
      temp2:='';
      Compare_Display ;
END;--output
Word to compare:test
temp:testttt
temp2:not assigned
    --- after the assignation --->
temp:testttt
temp2:NOT identic
Word to compare:test
temp:test
temp2:not assigned
    --- after the assignation --->
temp:test
temp2:identic
PS:for more explanations related to all the cases you could look for at http://tahiti.oracle.com/
Edited by: zep111 on Apr 28, 2011 11:25 AM

Query code cotains Syntax Errors

Hello Experts,
In the process of upgrading from 4.6 to 6.0 ECC SAP version, we had some issues at the moment of testing Queries from SQ01 transaction, nevertheless almost all the problems with queries were solved by regenerating them all over again from SQ01 for Queries and SQ02 for Infosets.
Everything was OK so far, until I tested this Query related to PCH Logical Database and realized that It had Syntax Errors and can't run, and the other 5 Queries related to the same Logical Database are having the same Syntax Errors and they can not be fixed by executing the Query from SQ01 or regenerating the Infoset (PCHORG) from SQ02.
I guess the Syntax Errors must be fixed by regenerating the code in the new version, but how can I do this?
Or, is there another process I am skipping to achieve this?
Any ideas on this?
Thanks in advance!

Hello VitorDFPinheiro thanks for your answer,
I tried to modify the errors manually but in first Instance this is not possible whitout an Access Key and secondly I think this is not the best practice due the code for queries is generated Automaticaly.
Nevertheless I tried to correct this syntax errors by copying the code and pasted it into a new Z program and compile it, the compiler threw even more errors when I corrected the first one, so I think that this is not the way to procced.
I guess that there should be a way to "regenerate" the query and this "regeneration" must reorganize the code and its syntax.
Any other suggestions?
Edited by: memo_cv on Oct 11, 2010 6:56 PM

Syntax errors for smarty code

I work with smarty a lot, and I mean a lot. Every single day in fact, all day long. Is there a way to turn off the syntax errors for my smarty code? Basically every file I open is going to tell me there are syntax errors all over the page...
Thanks!

I am not familiar with smarty but the options for disabling syntax errors can be found under the view menu,
View > Code View Options > Syntax Error Alerts in Info Bar (tick or untick)
Richard

Syntax error in code

Hi everyone,
Can anyone please tell me what is the syntax error in the following code when run in 11g.
FUNCTION plch_func (check_in IN BOOLEAN)
RETURN VARCHAR2
AS
BEGIN
RETURN CASE
WHEN check_in THEN '123'
WHEN TRUE THEN '456'
--WHEN SYSDATE < plch_now () THEN '789'
END ;
END plch_func;
Thanks.

Hi,
Are you getting any errors, cannot see anything wrong (syntactically).
SQL> CREATE OR REPLACE FUNCTION plch_func (check_in IN BOOLEAN)
2    RETURN VARCHAR2 AS
3 BEGIN
4    RETURN CASE
5             WHEN check_in THEN '123'
6             WHEN TRUE THEN '456'
7           --WHEN SYSDATE < plch_now () THEN '789'
8           END;
9 END plch_func;
10 /
Function created.
SQL>Regards
Peter

SYntax error - on Perform Statement

Hello friends,
I have a syntax error in the following code.
the error is      The field "P_I_PA0000" is unknown, but there are the following fields
in the function module.
Any suggestions.
Thanks,
Raju.
PARAMETERS: ps_file1like rlgrap-filename         " Incoming file 1
                DEFAULT 'c:\HR\ZCNV0008.txt' LOWER CASE,
DATA: BEGIN OF i_pa0000 OCCURS 100.
        INCLUDE STRUCTURE pa0000.
DATA: END OF i_pa0000.
PERFORM upload_local_file USING ps_file1
                         CHANGING i_pa0000[].
*&      Form upload_local_file
      text
     -->P_PS_FILE1 text
     <--P_I_PA0000 text
FORM upload_local_file USING    p_ps_file1
                        CHANGING p_i_pa0000[].
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                = p_ps_file1
      filetype                = 'ASC'
    TABLES
      data_tab                = p_i_pa0000[]
    EXCEPTIONS
      file_open_error         = 1
      file_read_error         = 2
      no_batch                = 3
      gui_refuse_filetransfer = 4
      invalid_type            = 5
      no_authority            = 6
      unknown_error           = 7
      bad_data_format         = 8
      header_not_allowed      = 9
      separator_not_allowed   = 10
      header_too_long         = 11
      unknown_dp_error        = 12
      access_denied           = 13
      dp_out_of_memory        = 14
      disk_full               = 15
      dp_timeout              = 16
      OTHERS                  = 17.
ENDFORM.                    " upload_local_file

If it doesn't work, why did you mark it as "solved"?
I think this is what you are trying to do:
PARAMETERS: ps_file1 LIKE rlgrap-filename " Incoming file 1
            DEFAULT 'c:\HR\ZCNV0008.txt' LOWER CASE.
DATA: BEGIN OF i_pa0000 OCCURS 100.
        INCLUDE STRUCTURE pa0000.
DATA: END OF i_pa0000.
PERFORM upload_local_file
        TABLES i_pa0000
        USING ps_file1.
*&      Form upload_local_file
*       text
FORM upload_local_file
    TABLES p_i_pa0000
    USING p_ps_file1.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                = p_ps_file1
      filetype                = 'ASC'
    TABLES
      data_tab                = p_i_pa0000
    EXCEPTIONS
      file_open_error         = 1
      file_read_error         = 2
      no_batch                = 3
      gui_refuse_filetransfer = 4
      invalid_type            = 5
      no_authority            = 6
      unknown_error           = 7
      bad_data_format         = 8
      header_not_allowed      = 9
      separator_not_allowed   = 10
      header_too_long         = 11
      unknown_dp_error        = 12
      access_denied           = 13
      dp_out_of_memory        = 14
      disk_full               = 15
      dp_timeout              = 16
      OTHERS                  = 17.
ENDFORM. " upload_local_file
Rob

ActionScript syntax errors are not detection with Flash Builder 4

I encountered a serious bug with Flash Builder 4, it is not showing ActionScript syntax error within an ActionScript class. How shall I fix this.
Best Regards,

Hi Mayank,
Please find the further details below:
Steps to Reproduce the bug:
1. Create a Flex Project (say Test for example)
2. Created a new ActionScript Class ABC.as within the Flex Project.
on typing the following code (and even after saving it)
package123 {
public1234 class ABC {
}blahblah123...
Expeteded Behavior:
ActionScript Editor should report an syntax errors with the following code.
Present Beharvior
no syntax error is detected. This is a regression in Flash Builder 4 as Flex Builder 3 detects ActionScript syntax error instantly (while typing).
Best Regards

Syntax error on query generation

Hi,
When I try to generate report syntax error occures. It's not a custom code. What do you think about it ?
(syntax error in the following code:
return.
perform Debug_xfems.
See some piece of generated file :
REPORT RSRRNAME.
FORM SELECT_4.
if G_S_QCF-cmess eq rrkg_C_cmess-error.
    perform CU_MESS_send.
endif.
    read Table <G_THX_s> assigning <G_SX_S>
         with table key k = G_SX_s-k.
    if sy-subrc gt 0.
      insert G_SX_S into table <G_THX_S> assigning <G_SX_S>.
    endif.
ENDFORM.
FORM MOVE_Z_SP_0001.
ENDFORM.
return.
perform Debug_xfems.
form check_fems using value(I_fems) type i.
perform I_fems of           " REP I_FEMS = 2
          MOVE_Z_SP_0001
          DEBUG_XFems.
endform.                      " now look at G_TSX_XFems
Thanks in advance.
Fiodar.

Hi,
I would suggest that you check OSS for existing SAP notes on the issue and if you find nothing, please create a SAP customer message.
All the best,
Mike

CR2011 - SQL Syntax Error

After updating our ODBC driver to match our current Unidata database version (7.1), we now get the following message from Crystal Reports 2011 on many of our existing reports:
"Failed to retrieve data from the database. Details: 37000:[Rocket U2][U2ODBC][1401249]Error ID: 21 Severity: ERROR Facility: DBCAPERR - SQL Syntax error. [Database Vendor Code: 5365440]
The generated SQL statement follows:
SELECT "INVCDETH_NF"."ITEM_NBR", "ITEMMAST_NF"."ITEM_DESC", "INVCDETH_NF"."SHIPPED_QUANTITY", "INVCDETH_NF"."Z_INV_DATE", "INVCDETH_NF"."Z_COMPANY", "INVCHDRH_NF"."INVOICE_TYPE", "INVCDETH_NF"."EXTENDED_PRICE", "INVCDETH_NF"."COST_OF_SALES", "INVCDETH_NF"."Z_PCC_CODE", "INVCDETH_NF"."DISCOUNT_AMOUNT", "INVCDETH_NF"."WAREHOUSE", "ITEMMAST_NF"."PRICE_CODE", "INVCHDRH_NF"."INVOICE_NBR", "INVCHDRH_NF"."REFERENCE_NBR"
FROM ("Administrators"."ITEMMAST_NF" "ITEMMAST_NF" INNER JOIN "Administrators"."INVCDETH_NF" "INVCDETH_NF" ON "ITEMMAST_NF"."ITEM_NBR"="INVCDETH_NF"."ITEM_NBR") INNER JOIN "Administrators"."INVCHDRH_NF" "INVCHDRH_NF" ON ((("INVCDETH_NF"."INVOICE_NBR"="INVCHDRH_NF"."INVOICE_NBR") AND ("INVCDETH_NF"."INV_HEADER_ID"="INVCHDRH_NF"."INV_HEADER_ID")) AND ("INVCDETH_NF"."REFERENCE_NBR"="INVCHDRH_NF"."REFERENCE_NBR")) AND ("INVCDETH_NF"."RELEASE_NBR"="INVCHDRH_NF"."RELEASE_NBR")
WHERE "INVCDETH_NF"."Z_COMPANY"='01' AND "INVCDETH_NF"."WAREHOUSE"='086' AND ("INVCDETH_NF"."Z_INV_DATE">={d '2013-12-08'} AND "INVCDETH_NF"."Z_INV_DATE"<={d '2013-12-26'})
ORDER BY "INVCDETH_NF"."WAREHOUSE"
I downloaded the trial version of CR2013 and get the same result. Can anyone shed any light? Thanks!

Yes, in that the query is what Crystal generated from the report being built in the designer. I simply copied it from the Database > Show SQL Query screen. Since the error I'm receiving is a SQL Syntax Error, I thought it would be appropriate to show it.
The bottom line is that because I am not very knowledgeable in SQL, I can't look at the query and identify the error. However, I am responsible for supporting CR in-house. Naturally, I have reported this to Rocket (the makers of the ODBC driver) but haven't received their reply yet.

ORA-20002: 501 Bad syntax error

Hi,
I intend to send a simple smtp mail using the builtin UTL_SMTP package.
But i get the following error:-
ORA-20002: 501 Bad syntax error
Here is my code:-
CREATE OR REPLACE PROCEDURE mail
IS
BEGIN
DECLARE
v_connection UTL_SMTP.CONNECTION;
BEGIN v_connection := UTL_SMTP.OPEN_CONNECTION(<my host here>,25);
dbms_output.put_line('Connection Opened');
UTL_SMTP.HELO(v_connection,<my host here>);
dbms_output.put_line('After calling helo');
UTL_SMTP.MAIL(v_connection,'[email protected]');
dbms_output.put_line('Sender set');
UTL_SMTP.RCPT(v_connection,'[email protected]');
dbms_output.put_line('Recipient Set');
UTL_SMTP.DATA(v_connection,'Sent From PL/SQL');
dbms_output.put_line('Message body set');
UTL_SMTP.QUIT(v_connection);
dbms_output.put_line('Connection Closed');
end;
END;
Here is the output:-
SQL> exec mail
Connection Opened
After calling helo
BEGIN mail; END;
ERROR at line 1:
ORA-20002: 501 Bad address syntax
ORA-06512: at "SYS.UTL_SMTP", line 86
ORA-06512: at "SYS.UTL_SMTP", line 204
ORA-06512: at "ADMIN.MAIL", line 13
ORA-06512: at line 1
I tried sending mails to my smtp server via java mailing API and i am
successful. So i am wondering wat i am doing wrong up there in Oracle.
I have JServer enabled, i also ran the initplsj.sql successfully.
Please help.
Regards,
Leo.

Hi APC,
Yep HELO returns 250. Here is the code i use followed by the output. I use valid e-mail addresses(changed them here cz they belong to real ppl :) ). Again, i am able to send mails via java mailing API's, to the same recipietn from same sender via same smtp server.
Code :------
CREATE OR REPLACE PROCEDURE mail
IS
v_connection UTL_SMTP.CONNECTION;
value UTL_SMTP.reply;
PROCEDURE send_header(name IN VARCHAR2, header IN VARCHAR2) AS
BEGIN
UTL_SMTP.write_data(v_connection, name || ': ' || header || utl_tcp.CRLF);
END;
BEGIN
v_connection := UTL_SMTP.OPEN_CONNECTION('smtp.server',25);
dbms_output.put_line('Connection Opened');
dbms_output.put_line('before calling helo');
value := UTL_SMTP.HELO(v_connection,'smtp.server');
dbms_output.put_line('after calling helo');
dbms_output.put_line('code ' || value.code);
dbms_output.put_line('before Sender is set');
value := UTL_SMTP.MAIL(v_connection,'[email protected]');
dbms_output.put_line('code ' || value.code);
dbms_output.put_line('text ' || value.text);
UTL_SMTP.RCPT(v_connection,'[email protected]');
dbms_output.put_line('Recipient Set');
UTL_SMTP.open_data(v_connection);
send_header('From','"Sender" <[email protected]>');
send_header('To','"Recipient" <[email protected]>');
send_header('Subject','Hello');
UTL_SMTP.write_data(v_connection, UTL_TCP.CRLF || 'Hello, world!');
UTL_SMTP.close_data(v_connection);
dbms_output.put_line('Message body set');
UTL_SMTP.QUIT(v_connection);
dbms_output.put_line('Connection Closed');
END;
Output:--------
Connection Opened
before calling helo
after calling helo
code 250
before Sender is set
code 501
text Bad address syntax
Looking forward to hearing from youself. :)
Reagrds,
Leo.

Report RV13A032 has a syntax error

When i try to create a Service and Maint contract, when i click Pricing Agreement, i get this error Report RV13A032 has a syntax error
Would any one know the source

It means that program RV13F004 has a syntax error in the ABAP code. Is this a generated program when doing condition records? I think yes, so you probably put some ABAP code in the condition, and it has written it to the generated program, Check the syntax of the coding that you had entered and make sure that it is correct.
Regards,
Rich Heilman

Syntax Error where ? ( CS5 )

I keep getting an error on this script, at line 3, but I can't see why?
<SCRIPT language="javascript">
function fillScreen()
{ self.moveTo(0,0);
self.resizeTo(screen.availWidth,screen.availHeight);
</SCRIPT>
self.moveTo(0,0); <--- Syntax Error on Dreamweaver CS5
Any Ideas ? Thanks

Most modern browsers will block your attempt to do this nasty trick, you know?
Your job is to make the web page accommodate all visitors, not make the visitors accommodate the web page.
CS5 is not giving me a syntax error with that antique code (I'm guessing it's vintage 1990 or thereabouts).
Why do you need it?

Designer syntax errors in correct code.

I have added some trigger code to a bound item. The designer syntax checker finds errors in the code but the generated form runs correctly. It appears that the syntax checker doesn't like DECLARE. The code doesn't do anything and I believe it is fine but I would like to get the syntax checker to stop complaining about it. Any suggestions on how I might arrange things to stop the syntax error messages would be appreciated. Here is the offending code with error messages:
DECLARE
item_id Item;
BEGIN
item_id := FIND_ITEM('M1.STATE');
END;
The Syntax Checker found the following errors:-
PLS-00103: (Line 1) Encountered the symbol "DECLARE" when expecting one of the following:
begin function package pragma procedure separate subtype type
use <an identifier> <a double-quoted delimited-identifier>
form current cursor external language
The symbol "begin" was substituted for "DECLARE" to continue.
PLS-00103: (Line 20) Encountered the symbol "end-of-file" when expecting one of the following:
begin case declare end exception exit for goto if loop mod
null pragma raise return select update while with
<an identifier> <a double-quoted d
[2] error(s), [0] warning(s)

This will not work correctly in 32-bit Windows (or 64-bit) The type of wParam *must* be WPARAM, the type of lParam *MUST* be LPARAM, and for a dialog handler the return type should be BOOL. The old _export keyword no longer exists, and is not needed in
Win32. FAR is a macro with an empty body and its appearance in all places can be deleted. The quaint and confusing PASCAL keyword may still work, but it would be better to use the now-correct term CALLBACK. Since this is clearly antique Win16 code, there may
be other problems dealing with size of integers. The types int, long, DWORD, UINT and others all represent 32-bit values. The return type for window handlers must have the return type LRESULT, and for dialog handlers, BOOL. All wParam and lParam types must
be changed as I indicated. Note that for Win16, wParam was 16-bit and lParam 32-bit. For Win32, WPARAM, LPARAM and LRESULT are all 32-bit values, and for Win64 they are 64-bit values. Any place the code casts a pointer to an integer type, the code is inherently
incorrect. You must use types like INT_PTR, UINT_PTR, DWORD_PTR and other _PTR-suffixed types for such casts; in Win32 these are pointer-sized integer types (32-bit) and in Win64 they are pointer-sized integer types (64-bit). Types like int, long, DWORD, etc.
are 32-bit values in both Win32 and Win64. Converting code to run on Win32/64 from Win16 requires great caution, because the programming "standards" that were taught for Win16 did not plan on true platform portability, and programmers were taught
terrible techniques such as declaring wParam as WORD and LPARAM as long. And casting pointers to ints and back. All of these techniques lead to disaster.

Syntax errors in old C++ code

Similar Messages

Maybe you are looking for