Activity
From 08/18/2021 to 09/16/2021
09/16/2021
- 07:16 PM Feature #4366 (Closed): support TLS 1.2 and other updated secure socket protocols
- 06:26 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- What other variety of tests would be helpful? Do these results coincide with expected results? To me it looks like ne...
- 01:35 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Below are my findings... I hope the table looks OK.
|\2/2. |_\7. Server |
... - 11:42 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Roger Borrello wrote:
> Because I am unworthy! Awesome!
Haha 😀!
> Let me follow-up with a question. If I have a ... - 10:27 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Ovidiu Maxiniuc wrote:
> Why not re-arrange the table as:
Because I am unworthy! Awesome!
Let me follow-up wit... - 09:02 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Roger Borrello wrote:
> I guess there are a limited number of permutations to deal with. Below is my testplan:
Why ... - 08:50 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Roger Borrello wrote:
> There is a pre-configuration step to perform, outside of the programming to generate:
> * t... - 08:09 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- > I wanted to check that when the server is setup for ssl and the client is tls, we can still connect, but the data i...
- 02:33 PM Feature #4384: Builtin OO Implementation
- Marian: In 4384m, would you please resolve these javadoc errors....
- 10:59 AM Feature #4384: Builtin OO Implementation
- Task branch 4384m has been created from 3821c revision 12935. This is available on xfer (@/opt/fwd/4384m/@).
- 10:28 AM Feature #4384: Builtin OO Implementation
- Marian, my only issue is that in @oo.core.Assert@ you've replaced @ObjectOps.load(Assert.class);@ with @ObjectOps.loa...
- 09:23 AM Feature #4384: Builtin OO Implementation
- Greg Shah wrote:
> It is safe to go ahead and make a patch using 12922. We'll merge that back quickly and get you a... - 08:31 AM Feature #4384: Builtin OO Implementation
- It is safe to go ahead and make a patch using 12922. We'll merge that back quickly and get you a new branch.
- 01:12 AM Feature #4384: Builtin OO Implementation
- Greg Shah wrote:
> I think we've definitely made many fixes that may affect you. Let's go through the rebase + merg... - 01:56 PM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Please note that we will need to update the font metrics calculation to process all the translations. And we will ne...
- 01:42 PM Feature #3817: create resource bundles from string literals and implement optional support for se...
- > As a corollary, an external procedure ran non-persistently, with no outstanding persistent instances, can be invoke...
- 01:12 PM Feature #3817: create resource bundles from string literals and implement optional support for se...
- To support the conversion path for customers using OE translation workflow, the translations can be "dumped" from Tra...
- 01:07 PM Feature #3817: create resource bundles from string literals and implement optional support for se...
- See my findings below. I will update this note as I go.
Greg Shah wrote:
> +Areas to Investigate+
>
> * Write ...
09/15/2021
- 06:47 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- I guess there are a limited number of permutations to deal with. Below is my testplan:
|_. Server |_. Client |_. R... - 06:04 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- I can finally accomplish the testing. I wanted to check that when the server is setup for @ssl@ and the client is @tl...
- 05:36 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Well it was just a matter of time before I figured out what I was doing wrong. I hadn't noticed that there were 2 sep...
- 03:36 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- I run the tests only from my workstation. No network changes required. The parameters look fine, I am positive the fi...
- 02:36 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- I am troubled by the fact that I can use my current configuration with the @sockets/server-connect.p@ and @sockets/cl...
- 02:24 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Roger Borrello wrote:
> Ovidiu, thank you for all those pointers. Thanks to them, I was successful in making sure th... - 02:11 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- > I think that the wiki should be a little more step-by-step with the example, including basic passwords for the stor...
- 02:00 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Ovidiu, thank you for all those pointers. Thanks to them, I was successful in making sure the store password and the ...
- 09:33 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- I understand now. And I have just noticed the "keystore" password commented in your note-57.
The problem is that y... - 05:30 PM Bug #5651: conditions raised from a finally block
- I am willing to postpone the implementation of @NEXT@ in a @FINALLY@. We can put code in to detect this at conversio...
- 04:43 PM Bug #5651: conditions raised from a finally block
- And something I didn't expect: same suite ran in ChUI and GUI (OE 11.6.3) gives different results in ~5% of cases. T...
- 04:33 PM Bug #5651: conditions raised from a finally block
- Ughhh. Supporting @NEXT@ in a finally which overrides a prior @LEAVE@ is an awful "feature" and a terrible idea. Wh...
- 02:43 PM Bug #5651: conditions raised from a finally block
- Greg, there is an issue which is kind of tricky. For looping blocks, the finally can not be processed at the @popSco...
- 09:26 AM Feature #4384: Builtin OO Implementation
- I think we've definitely made many fixes that may affect you. Let's go through the rebase + merge process and then g...
- 08:45 AM Feature #4384: Builtin OO Implementation
- Constantin Asofiei wrote:
> Please try this patch and see if anything changes:
Better, thanks a bunch :)
- 08:27 AM Feature #4384: Builtin OO Implementation
- Argh, think we need to get to a newer revision as this might be the cause for more other errors we see because the ob...
- 08:26 AM Feature #4384: Builtin OO Implementation
- Please try this patch and see if anything changes:...
- 08:16 AM Feature #4384: Builtin OO Implementation
- Constantin Asofiei wrote:
> What 3821c revision are you on? We had some issues with destructors which were not being... - 08:08 AM Feature #4384: Builtin OO Implementation
- What 3821c revision are you on? We had some issues with destructors which were not being called at all, fixed in Obje...
- 07:53 AM Feature #4384: Builtin OO Implementation
- I see a bunch of unexpected errors being thrown when we ran all tests for OpenEdge.Core.Memptr, #1005 (Procedure xxx ...
09/14/2021
- 05:39 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- OK... because I am having issues with the below, I'll flip-flop the passwords. I get @Unable to prtocess parameters. ...
- 04:52 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- The problem is here:
> @-Dssl-socket:keystore:password=keystore@
In fact, there are two of them:
# use @password@ ... - 04:31 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- This is what I did (still resulting in the tampered error)....
- 08:31 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Here are a few notes about building the Adetran project. These are on top of the existing documentation.
h2. Build...
09/13/2021
- 03:10 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Roger,
Your key loads in my test procedure(s). They are the exactly the same from @Socket Handle and Server Socket H... - 01:36 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- That error I get when the password is somehow incorrect. Can you send me the @default_server.store@ you've generated.
- 12:32 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Ovidiu, I am trying to follow the wiki, and my server source code is the same as your example (except I am using a va...
09/10/2021
- 04:00 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Yes, the "working" directory is the right work. I have just updated the wiki.
- 03:49 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- In your text, you mention "This .store container must be located in root directory of the FWD-client" and "trusted-ce...
- 02:17 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> Ovidiu: Please document the specific requirements. We may need to make code changes to make it e... - 02:03 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Roger Borrello wrote:
> Ovidiu, I was using @SSLCertGenUtil@ to do the generation of the keys into the directory ("s... - 07:04 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Passing the output from the SSLCertGenUtil cannot work since it is not encoded as hex.
Ovidiu: Please document t... - 07:28 AM Feature #4384: Builtin OO Implementation
- Greg Shah wrote:
> > * @SERIALIZABLE@ keyword should probably be used by conversion to make the class implement @Ser...
09/09/2021
- 06:29 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> Roger: Please ask Ovidiu specific questions to get help with this configuration. Also, after Ovi... - 09:46 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Ovidiu: Please edit [[p2j:Certificates_and_Keys_for_4GL_Language_Features#Socket-Handle-and-Server-Socket-Handle-SSL-...
- 08:26 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- If you look at the code for @SymmetricEncryption.decrypt()@, you'll see that in @asBytes()@ it assumes that the input...
- 08:17 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> Is that what you expect? If the actual key password has 2 tildes, then you need to double them i... - 07:15 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- The tilde is an escape char in the 4GL. If your code is this:
@define variable kapw as char init "v~~4l#8ZrkkJwW?...
09/08/2021
- 06:20 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- I am back to testing with my testcases...the @ssl-server.p@ has:...
- 04:21 PM Feature #4366 (Test): support TLS 1.2 and other updated secure socket protocols
- Code Review Task Branch 3821c Revision 12901
The changes look good. - 03:27 PM Feature #4366 (Feedback): support TLS 1.2 and other updated secure socket protocols
- Please review:...
- 08:18 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> > This is not correct, there is no @LowLevelSocketImpl@ usage for the @WebServiceImpl@ at this ti... - 07:33 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- > This is not correct, there is no @LowLevelSocketImpl@ usage for the @WebServiceImpl@ at this time.
Does anyone k... - 04:25 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> +WEB-SERVICE:CONNECT()+
>
> On the server, a call to @<web_service_handle>:CONNECT()@ will pa... - 12:26 PM Feature #5662: add -WSDLAuth and -SSLAuth (and related) connect options for the web-services handle
- These connect options (and the key/cert related options) were added after OE 10.2B which was the initial implemented ...
- 12:24 PM Feature #5662 (New): add -WSDLAuth and -SSLAuth (and related) connect options for the web-service...
- 10:08 AM Bug #4766: fix CHR and ASC
- Code Review Task Branch 3821c Revision 12898
The changes look good. - 08:25 AM Feature #4384: Builtin OO Implementation
- > * @SERIALIZABLE@ keyword should probably be used by conversion to make the class implement @Serializable@ so we can...
- 04:49 AM Feature #4384: Builtin OO Implementation
- Going through all tests to see if still passing, update implementation as needed (other changes did impact the test r...
09/07/2021
- 05:03 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- > but we still need a way to determine what to pass in the #4366-21 when @LowLevelSocketImpl.initialize@ creates the ...
- 03:08 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> I don't know for sure, but I suspect that @LowLevelSocketListenerImpl.enableSSLConnections()@ sho... - 02:34 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- I don't know for sure, but I suspect that @LowLevelSocketListenerImpl.enableSSLConnections()@ should be using @"SSL"@.
- 02:23 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- In examining the difference between the @src/com/goldencode/p2j/util/LowLevelSocketImpl.java@ and @src/com/goldencode...
- 10:56 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- First, let's note that the various versions of SSL are not the same as the various TLS versions. There are slight in...
- 10:21 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> Perhaps we should force it to the 1.2 level. Since a v1 or v1.1 peer can negotiate the connectio... - 04:09 PM Bug #4766: fix CHR and ASC
- The fix for @chr(0)@ was committed in revision 12898/3821c.
- 09:12 AM Bug #4766: fix CHR and ASC
- Nice catch. The problem is not actually in @I18nOps@ (which converts @chr(0)@ to @"\0"@) but in @character@ construct...
- 08:39 AM Bug #4766: fix CHR and ASC
- Ovidiu Maxiniuc wrote:
> Marian Edu wrote:
> > [...] There was previously a condition in @I18nOps@ that returned nu... - 08:26 AM Bug #4766: fix CHR and ASC
- Marian Edu wrote:
> [...] There was previously a condition in @I18nOps@ that returned null for codes less or equal t... - 08:14 AM Bug #4766: fix CHR and ASC
- Marian, please provide the (isolated) testcases you refer to in note #4766-5. Please specify the active CP(s) you are...
- 07:06 AM Bug #4766: fix CHR and ASC
- This is probably still a work in progress but just mentioned this here since we've found some of our tests in OO impl...
09/06/2021
- 03:49 PM Bug #5651: conditions raised from a finally block
- I think we need to handle all the cases now. We can't know what minor edit will cause new cases to be used tomorrow ...
- 09:55 AM Bug #5651: conditions raised from a finally block
- I just found that another customer application is using @RETURN "<val>"@ from the finally block.
I'll right a repo... - 07:27 AM Bug #5651: conditions raised from a finally block
- I think you can go ahead with the change.
09/04/2021
- 05:49 AM Bug #5651: conditions raised from a finally block
- Greg Shah wrote:
> Agreed. Please put a new try/finally in like this from @processRetry()@:
>
> [...]
>
> I d...
09/03/2021
- 02:32 PM Bug #5651: conditions raised from a finally block
- Make sure to put your testcases in @testcases/uast/finally/@ and update the readme there.
- 02:32 PM Bug #5651: conditions raised from a finally block
- > My first problem is that I don't see how to distinguish between @undo, leave@ and @leave@, when is caught via @Leav...
- 01:58 PM Bug #5651 (WIP): conditions raised from a finally block
- Looks like the following are consumed from a @finally@ block:...
- 12:00 PM Bug #5651: conditions raised from a finally block
- @TransactionManager.processFinallyBlock@ is not protected at all for conditions raised from within the finally block....
- 11:54 AM Bug #5651 (WIP): conditions raised from a finally block
- 01:54 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Perhaps we should force it to the 1.2 level. Since a v1 or v1.1 peer can negotiate the connection down to the older ...
- 12:51 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Roger Borrello wrote:
> Igor Skornyakov wrote:
> > Roger,
> > As far as I know the TLS versions prior to 1.2 are c... - 12:46 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Igor Skornyakov wrote:
> Roger,
> As far as I know the TLS versions prior to 1.2 are considered obsolete now. Since... - 10:28 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Roger Borrello wrote:
> Ovidiu, Igor, is there any need to allow the custom @SSLProtocolSocketFactory@ defined in th... - 10:19 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Ovidiu, Igor, is there any need to allow the custom @SSLProtocolSocketFactory@ defined in the @LowLevelSocketImpl.ini...
- 09:06 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> @ThinClient.initializePost()@ is only called once at startup of the session so it is not suitable... - 08:55 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Thanks for the tips... I'll take a look.
- 07:27 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- > I have most all of this task coded up, but I am unsure of one aspect. I have added a String protocol parameter that...
09/02/2021
- 05:33 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- I have most all of this task coded up, but I am unsure of one aspect. I have added a *String protocol* parameter that...
- 03:23 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> I like your original idea of providing a range of string parameters. If the chosen secure socket... - 02:31 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- > perhaps we should just have -tls as an additional option, which would generate the TLSv1.2 context?
No, I think ... - 02:25 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- When @-ssl@ is passed in the @ENABLE-CONNECTIONS@ string @LowLevelSocketListerner.enableSSLConnections@ performs:
<p... - 11:46 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Ovidiu Maxiniuc wrote:
> Most likely at this point @keyStorePassword@ was an empty @String@.
Thanks, Ovidiu. That... - 07:54 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Roger Borrello wrote:
> It's not a question of getting hung up. I would expect that for any algorithm I add, there w... - 09:10 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- The attached is the zipped archive of the https://github.com/gquerret/adetran project sources. I'm also attaching the...
- 08:48 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Hynek alerted me to the following interesting articles:
https://knowledgebase.progress.com/articles/Article/Transl... - 07:21 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Yes, but you should base it on 3821c.
- 07:04 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Greg, should I create new task branch for the changes?
- 07:01 AM Feature #3817 (WIP): create resource bundles from string literals and implement optional support ...
09/01/2021
- 06:40 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> Please see #2181 for details on the existing 4GL-compatible SSL socket support. Search on "keyst... - 03:15 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Please see #2181 for details on the existing 4GL-compatible SSL socket support. Search on "keystore" and "default_se...
- 03:08 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Constantin Asofiei wrote:
> I suspect the correct location is in the @deploy/client@ folder or wherever the FWD clie... - 02:47 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- I suspect the correct location is in the @deploy/client@ folder or wherever the FWD client working dir is.
- 02:45 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Actually, the @keyStoreName@ cannot be found. I tried to copy @./deploy/server/standard-private-key.store@ to @defaul...
- 02:42 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- > @KeyStore ks = KeyStore.getInstance("JKS"); <-- I believe this comes back null@
That doesn't so... - 01:02 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- The testcases I found in @uast/sockets@ and @uast/sockets/ssl@ are very helpful. However, I may need a little help co...
- 06:39 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- And which doesn't conflict with existing syntax from the 4GL.
- 06:38 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- It is our own syntax. This is a new feature/enhancement. Just make the syntax anything that makes sense and is easy...
08/31/2021
- 04:59 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Does 4GL already have syntax to enable this? Or are we making up our own?
In looking for the best documentation, i... - 08:16 AM Bug #5635: OpenEdge.Core.Util.ConfigBuilder implementation
- The current implementation is not fully compatible with 4GL because is is using a @Map@ to store the key/value pairs ...
- 08:16 AM Bug #5635 (New): OpenEdge.Core.Util.ConfigBuilder implementation
08/20/2021
- 12:07 PM Bug #5613: 4GL built-in functions throw IllegalArgumentException
- Please make a list of all of the cases you have found. It is OK to just list the names of the 4GL programs in the @t...
- 11:32 AM Bug #5613: 4GL built-in functions throw IllegalArgumentException
- Greg Shah wrote:
> Igor: Let's avoid using the term "UDF" here since that is specific to database WHERE clause execu... - 10:52 AM Bug #5613: 4GL built-in functions throw IllegalArgumentException
- Igor: Let's avoid using the term "UDF" here since that is specific to database WHERE clause execution. The problem h...
- 10:50 AM Bug #5613: 4GL built-in functions throw IllegalArgumentException
- From Igor:
> Some Java counterparts of 4GL functions which are called directly from the converted code can throw @... - 10:50 AM Bug #5613 (New): 4GL built-in functions throw IllegalArgumentException
- 11:06 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Greg Shah wrote:
> The plan is good.
>
> > 3. Implement conversion rules to emit required Java code - any bundle ... - 10:59 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- The plan is good.
> 3. Implement conversion rules to emit required Java code - any bundle initialization logic, ge... - 10:52 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- In order to estimate the efforts I came up with the following sub tasks:
1. Resolve the unknowns laid out by Greg ... - 09:34 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Greg Shah wrote:
> * The 4GL essentially has resource-bundles that are specific to a single program. This may have ... - 09:28 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Depending on the @CURRENT-LANGUAGE@ scope, the resource bundle will have to be scoped accordingly. The possible outco...
- 08:08 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Hynek Cihlar wrote:
> Greg Shah wrote:
> > +FWD Implementation Questions+
> >
> > * To match the behavior of the... - 07:51 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- > I assume the scope includes translation of FWD runtime, too. Like error messages. Correct?
No, we will handle th... - 03:02 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Greg Shah wrote:
> +FWD Implementation Questions+
>
> * To match the behavior of the 4GL
Greg, what behavior ... - 02:30 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- I assume the scope includes translation of FWD runtime, too. Like error messages. Correct?
08/18/2021
- 01:01 PM Bug #5608: raw vs memptr parameters
- @testcases/uast/memptr/memptr_vs_raw.p@ has some tests where raw/memptr args are passed for memptr/raw parameters. F...
- 12:56 PM Bug #5608 (New): raw vs memptr parameters
- 10:13 AM Bug #2375: fix the memptr initialization (in extent) and memptr parameter processing
- Greg Shah wrote:
> In @public raw(byte[] val)@, I think this text needs to be removed from the javadoc: "The passed ... - 09:17 AM Bug #2375 (Closed): fix the memptr initialization (in extent) and memptr parameter processing
- Code Review Task Branch 3821c Revision 12835
The solution is elegant and it makes sense.
In @public raw(byte[] ... - 06:19 AM Bug #2375 (Review): fix the memptr initialization (in extent) and memptr parameter processing
- The changes are in 3821c rev 12835.
- 05:33 AM Bug #2375: fix the memptr initialization (in extent) and memptr parameter processing
- The 'memptr is both unknown and not-unknown' seems to not happen in Windows OE 11.6. Do you recall if the #1635-31 w...
- 02:17 AM Feature #4350: method overload when they differ by a temp-table, dataset, buffer or object or ext...
- Greg Shah wrote:
> I'm confused by this code in @symbolResolver.loadConvertedClass()@:
>
> [...]
>
> Why do we...
Also available in: Atom