Skip to Content
author's profile photo Former Member
Former Member

PowerBuilder Classic 15 beta error

Doing some initial testing with PowerBuilder Classic 15 beta against our applications. Some migrate ok, however there is one set of apps which are generating an error. This group of apps leverage the PFC as well as a custom library which is itself leveraging the PFC. These application work perfectly under 12.5.2 classic (and below).

When migrating, we are getting the following error in a popup: "Invalid type in cm_intrinsic_int, file cmintrin.cpp, line 375" Our applications don't have such a file so I'm guessing this is something internal to PowerBuilder. I am also given Abort, Ignore, Retry buttons so I just ignore. Everything 'seems' ok as I can open the object in question, but when trying to regenerate this specific object, the same error appears.

I guess this is why we test beta software.

Other than this issue, things looking good so far but I'm early in testing..

Any ideas/suggestions would be great.

Shane Maitland

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 02, 2014 at 08:32 PM

    Shane,

    Is it possible to narrow it down further to the line of code by 'commenting out' some of the code?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Ummm....there's a whole lotta code there. I was afraid this might come up. 😢

      I'm going to try and pull out only the specific objects required. Being this is inter-twined with the PFC, this may take some work.

      Once I have this pulled-out, I'll see what I can do to narrow down

      Shane

  • Posted on Jan 02, 2014 at 08:37 PM

    Outch.. I am getting this error while accessing message.WordParm in the follwing way...

    ls_test = Char(int(message.WordParm))

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 03, 2014 at 08:17 PM

    If the compiling is base on 32/64bits, then the Int assertion failure should also be based on the same. It sounds like the Int function assertion hasn't been re-written to obey the new rules, or isn't quite right. There should be no need to re-write the sle search script, it should behave as expected in converting WordParam to an Int. (basically, when you convert 64bits to 32bits (or 16), you're basically just taking the lowest appropriate # of bits and discarding everything else)

    Aside from that, a new variable type to match the Windows API definition should make coding DLL calls less tricky when compiling for 32/64bit environments (same definition will work for both).

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.