Skip to Main Content
Forums

Java APIs

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

After compiling classes with generics, can types still be params?

843793Jul 30 2002 — edited Jul 31 2002

Hello,

As I understand it, generics types are a feature of the compiler, not the compiled class. So if I compile some classes (containing parameterized types/generics), the compiler helps check type safety. But once they're compiled, if generics really are just "a compiler features", in any other Java code that I write that refers to the compiled classes, it seems perfectly possible that I could refer to methods in the compiled class using inappropriate casts/types, because the generic information is present in the source code, and no longer present in the compiled class.

This seems to be a big limitation, as it would mean I'd lose the benefits of generics when working with the core API or compiled classes (especially likely with JAR files...). I must be missing something here, anyone able to help me understand how parameterized types can be used when referring to compiled classes (for which I don't have access to the source code) from my own Java code?

Thanks,
Chris B.

Comments

Yoda-Oracle

Hi,

Your Zone now has 16GB of RAM. Please let me know if that is sufficient

-Angelo

1336415

Thank you. Now memory limit is sufficient.

But CPU offloading still shows that while DAX doing its work - CPU core busy too.

With new memory limit vector_in_range() takes 0,8 seconds to complete. Let's run it in cycle on the same thread id with "yes > /dev/null" (using pbind). Again, we see that yes shares CPU time with dax-in-range:

   PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWP  

19860 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0  30 34K   0 yes/1

19868 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0  30 34K   0 yes/1

19864 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0  30 34K   0 yes/1

19866 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0  30 34K   0 yes/1

19857 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0  30 34K   0 yes/1

19862 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0  30 34K   0 yes/1

19870 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0  30 34K   0 yes/1

19880 dglushe* 50  15 0.1 0.0 0.0 0.0 0.0  35   1  23 .1M 0 dax-in-range/1

19850 dglushe*  34 0.3 0.0 0.0 0.0 0.0 0.0  65 0  24 10K   0 yes/1

1336415
Answer

Oh, I see you shared dax.h. It seems that vector.so uses synchronous DAX calls, but dax.h states that there are asynchronous calls too:

/* 


    NAME: dax_post - family of functions that post asynchronous dax requests


    SYNOPSIS:


  */


..







dax_status_t dax_scan_range_post(dax_queue_t *queue, uint64_t flags,





    dax_vec_t *src, dax_vec_t *dst, dax_compare_t op, dax_int_t *lower,





    dax_int_t *upper, void *udata);


No more questions, thank you!

Marked as Answer by 1336415 · Sep 27 2020
1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Aug 28 2002
Added on Jul 30 2002
#generics
3 comments
85 views