Object源码

// 注释是我写的内容,对一些单词做了查找。

package java.lang;/*** Class {@code Object} is the root of the class hierarchy(英  [ˈhaɪərɑːki],n. 层级;等级制度).* Every class has {@code Object} as a superclass. All objects,* including arrays, implement the methods of this class.** @author  unascribed* @see     java.lang.Class* @since   JDK1.0*/
public class Object {private static native void registerNatives();// 当jvm加载类时,静态代码块的内容会先于其他代码块执行,且只会被执行一次static {registerNatives();}/*** Returns the runtime class of this {@code Object}. The returned* {@code Class} object is the object that is locked by {@code* static synchronized(英  ['sɪŋkrənaɪzd],adj. 同步的;同步化的)} methods of the represented( 英  [reprɪ'zentɪd],v. 代表;表现;描写(represent的过去分词)) class.** <p><b>The actual result type is {@code Class<? extends |X|>}* where {@code |X|} is the erasure of the static type of the* expression on which {@code getClass} is called.</b> For* example, no cast is required in this code fragment:</p>** <p>* {@code Number n = 0;                             }<br>* {@code Class<? extends Number> c = n.getClass(); }* </p>** @return The {@code Class} object that represents the runtime*         class of this object.* @jls 15.8.2 Class Literals*/public final native Class<?> getClass();/*** Returns a hash code value for the object. This method is* supported for the benefit of hash tables such as those provided by* {@link java.util.HashMap}.* <p>* The general contract of {@code hashCode} is:* <ul>* <li>Whenever it is invoked on the same object more than once during*     an execution of a Java application, the {@code hashCode} method*     must consistently return the same integer, provided no information*     used in {@code equals} comparisons on the object is modified.*     This integer need not remain consistent from one execution of an*     application to another execution of the same application.* <li>If two objects are equal according to the {@code equals(Object)}*     method, then calling the {@code hashCode} method on each of*     the two objects must produce the same integer result.* <li>It is <em>not</em> required that if two objects are unequal*     according to the {@link java.lang.Object#equals(java.lang.Object)}*     method, then calling the {@code hashCode} method on each of the*     two objects must produce distinct integer results.  However, the*     programmer should be aware that producing distinct integer results*     for unequal objects may improve the performance of hash tables.* </ul>* <p>* As much as is reasonably practical, the hashCode method defined by* class {@code Object} does return distinct integers for distinct* objects. (This is typically implemented by converting the internal* address of the object into an integer, but this implementation* technique is not required by the* Java&trade; programming language.)** @return  a hash code value for this object.* @see     java.lang.Object#equals(java.lang.Object)* @see     java.lang.System#identityHashCode*/// 如果两个对象调equals()返回true,则他们调hashCode()应该相同// 覆盖equals()时总要覆盖hashCode()public native int hashCode();/*** Indicates(v. 表明(indicate的第三人称单数形式);指示,显示) whether some other object is "equal to" this one.* <p>* The {@code equals} method implements an equivalence relation* on non-null object references:* <ul>* <li>It is <i>reflexive</i>: for any non-null reference value*     {@code x}, {@code x.equals(x)} should return*     {@code true}.* <li>It is <i>symmetric</i>: for any non-null reference values*     {@code x} and {@code y}, {@code x.equals(y)}*     should return {@code true} if and only if*     {@code y.equals(x)} returns {@code true}.* <li>It is <i>transitive</i>: for any non-null reference values*     {@code x}, {@code y}, and {@code z}, if*     {@code x.equals(y)} returns {@code true} and*     {@code y.equals(z)} returns {@code true}, then*     {@code x.equals(z)} should return {@code true}.* <li>It is <i>consistent</i>: for any non-null reference values*     {@code x} and {@code y}, multiple invocations of*     {@code x.equals(y)} consistently return {@code true}*     or consistently return {@code false}, provided no*     information used in {@code equals} comparisons on the*     objects is modified.* <li>For any non-null reference value {@code x},*     {@code x.equals(null)} should return {@code false}.* </ul>* <p>* The {@code equals} method for class {@code Object} implements* the most discriminating possible equivalence relation on objects;* that is, for any non-null reference values {@code x} and* {@code y}, this method returns {@code true} if and only* if {@code x} and {@code y} refer to the same object* ({@code x == y} has the value {@code true}).* <p>* Note that it is generally( 英  [ˈdʒenrəli]) necessary to override the {@code hashCode}* method whenever this method is overridden, so as to maintain the* general contract for the {@code hashCode} method, which states* that equal objects must have equal hash codes.** @param   obj   the reference object with which to compare.* @return  {@code true} if this object is the same as the obj*          argument; {@code false} otherwise.* @see     #hashCode()* @see     java.util.HashMap*/// 自反性// 对称性// 传递性// 一致性// 任何非null的x,调用x.equals(null)必返回falsepublic boolean equals(Object obj) {return (this == obj);}/*** Creates and returns a copy of this object.  The precise meaning* of "copy" may depend on the class of the object. The general* intent is that, for any object {@code x}, the expression:* <blockquote>* <pre>* x.clone() != x</pre></blockquote>* will be true, and that the expression:* <blockquote>* <pre>* x.clone().getClass() == x.getClass()</pre></blockquote>* will be {@code true}, but these are not absolute requirements.* While it is typically the case that:* <blockquote>* <pre>* x.clone().equals(x)</pre></blockquote>* will be {@code true}, this is not an absolute(英  [ˈæbsəluːt],adj. 绝对的;完全的;专制的) requirement.* <p>* By convention, the returned object should be obtained by calling* {@code super.clone}.  If a class and all of its superclasses (except* {@code Object}) obey this convention, it will be the case that* {@code x.clone().getClass() == x.getClass()}.* <p>* By convention(英  [kənˈvenʃn],n. 大会;[法] 惯例;[计] 约定;[法] 协定;习俗), the object returned by this method should be independent* of this object (which is being cloned).  To achieve this independence,* it may be necessary to modify one or more fields of the object returned* by {@code super.clone} before returning it.  Typically, this means* copying any mutable objects that comprise the internal "deep structure"* of the object being cloned and replacing the references(references,n. [图情] 参考文献;参照;推荐信(reference的复数)) to these* objects with references to the copies.  If a class contains only* primitive fields or references to immutable(英  [ɪˈmjuːtəbl],adj. 不变的;不可变的;不能变的) objects, then it is usually* the case that no fields in the object returned by {@code super.clone}* need to be modified.* <p>* The method {@code clone} for class {@code Object} performs a* specific cloning operation. First, if the class of this object does* not implement the interface {@code Cloneable}, then a* {@code CloneNotSupportedException} is thrown. Note that all arrays* are considered to implement the interface {@code Cloneable} and that* the return type of the {@code clone} method of an array type {@code T[]}* is {@code T[]} where T is any reference or primitive type.* Otherwise, this method creates a new instance of the class of this* object and initializes(vt. 初始化(initialize的第三人称单数)) all its fields with exactly the contents of* the corresponding fields of this object, as if by assignment; the* contents of the fields are not themselves cloned. Thus, this method* performs a "shallow copy" of this object, not a "deep copy" operation.* <p>* The class {@code Object} does not itself implement the interface* {@code Cloneable}, so calling the {@code clone} method on an object* whose class is {@code Object} will result in throwing an* exception at run time.** @return     a clone of this instance.* @throws  CloneNotSupportedException  if the object's class does not*               support the {@code Cloneable} interface. Subclasses*               that override the {@code clone} method can also*               throw this exception to indicate that an instance cannot*               be cloned.* @see java.lang.Cloneable*/// 子类应该谨慎地覆盖clone()方法,clone()方法的通用约定较弱protected native Object clone() throws CloneNotSupportedException;/*** Returns a string representation([,reprizen'teiʃən],n. 代表;表现;表示法;陈述) of the object. In general, the* {@code toString} method returns a string that* "textually represents" this object. The result should* be a concise but informative representation that is easy for a* person to read.* It is recommended that all subclasses override this method.* <p>* The {@code toString} method for class {@code Object}* returns a string consisting of the name of the class of which the* object is an instance, the at-sign character `{@code @}', and* the unsigned hexadecimal representation of the hash code of the* object. In other words, this method returns a string equal to the* value of:* <blockquote>* <pre>* getClass().getName() + '@' + Integer.toHexString(hashCode())* </pre></blockquote>** @return  a string representation of the object.*/// 建议所有的子类都要覆盖此方法public String toString() {return getClass().getName() + "@" + Integer.toHexString(hashCode());}/*** Wakes up a single thread that is waiting on this object's* monitor. If any threads are waiting on this object, one of them* is chosen to be awakened. The choice is arbitrary(英  [ˈɑːbɪtrəri; ˈɑːbɪtri],adj. [数] 任意的;武断的;专制的) and occurs at* the discretion of the implementation. A thread waits on an object's* monitor by calling one of the {@code wait} methods.* <p>* The awakened thread will not be able to proceed until the current* thread relinquishes the lock on this object. The awakened thread will* compete in the usual manner with any other threads that might be* actively competing to synchronize on this object; for example, the* awakened thread enjoys no reliable privilege or disadvantage in being* the next thread to lock this object.* <p>* This method should only be called by a thread that is the owner* of this object's monitor. A thread becomes the owner of the* object's monitor in one of three ways:* <ul>* <li>By executing a synchronized instance method of that object.* <li>By executing the body of a {@code synchronized} statement*     that synchronizes on the object.* <li>For objects of type {@code Class,} by executing a*     synchronized static method of that class.* </ul>* <p>* Only one thread at a time can own an object's monitor.** @throws  IllegalMonitorStateException  if the current thread is not*               the owner of this object's monitor.* @see        java.lang.Object#notifyAll()* @see        java.lang.Object#wait()*/public final native void notify();/*** Wakes up all threads that are waiting on this object's monitor. A* thread waits on an object's monitor by calling one of the* {@code wait} methods.* <p>* The awakened threads will not be able to proceed until the current* thread relinquishes the lock on this object. The awakened threads* will compete in the usual manner with any other threads that might* be actively competing to synchronize on this object; for example,* the awakened threads enjoy no reliable privilege or disadvantage in* being the next thread to lock this object.* <p>* This method should only be called by a thread that is the owner* of this object's monitor. See the {@code notify} method for a* description of the ways in which a thread can become the owner of* a monitor.** @throws  IllegalMonitorStateException  if the current thread is not*               the owner of this object's monitor.* @see        java.lang.Object#notify()* @see        java.lang.Object#wait()*/public final native void notifyAll();/*** Causes the current thread to wait until either another thread invokes the* {@link java.lang.Object#notify()} method or the* {@link java.lang.Object#notifyAll()} method for this object, or a* specified amount of time has elapsed.* <p>* The current thread must own this object's monitor.* <p>* This method causes the current thread (call it <var>T</var>) to* place itself in the wait set for this object and then to relinquish* any and all synchronization claims on this object. Thread <var>T</var>* becomes disabled for thread scheduling purposes and lies dormant* until one of four things happens:* <ul>* <li>Some other thread invokes the {@code notify} method for this* object and thread <var>T</var> happens to be arbitrarily chosen as* the thread to be awakened.* <li>Some other thread invokes the {@code notifyAll} method for this* object.* <li>Some other thread {@linkplain Thread#interrupt() interrupts}* thread <var>T</var>.* <li>The specified amount of real time has elapsed, more or less.  If* {@code timeout} is zero, however, then real time is not taken into* consideration and the thread simply waits until notified.* </ul>* The thread <var>T</var> is then removed from the wait set for this* object and re-enabled for thread scheduling. It then competes in the* usual manner with other threads for the right to synchronize on the* object; once it has gained control of the object, all its* synchronization claims on the object are restored to the status quo* ante - that is, to the situation as of the time that the {@code wait}* method was invoked. Thread <var>T</var> then returns from the* invocation of the {@code wait} method. Thus, on return from the* {@code wait} method, the synchronization state of the object and of* thread {@code T} is exactly as it was when the {@code wait} method* was invoked.* <p>* A thread can also wake up without being notified, interrupted, or* timing out, a so-called <i>spurious(英  [ˈspjʊəriəs],adj. 假的;伪造的;欺骗的) wakeup</i>.  While this will rarely* occur in practice, applications must guard against(防止;提防) it by testing for* the condition that should have caused the thread to be awakened, and* continuing to wait if the condition is not satisfied.  In other words,* waits should always occur in loops, like this one:* <pre>*     synchronized (obj) {*         while (&lt;condition does not hold&gt;)*             obj.wait(timeout);*         ... // Perform action appropriate to condition*     }* </pre>* (For more information on this topic, see Section 3.2.3 in Doug Lea's* "Concurrent Programming in Java (Second Edition)" (Addison-Wesley,* 2000), or Item 50 in Joshua Bloch's "Effective Java Programming* Language Guide" (Addison-Wesley, 2001).** <p>If the current thread is {@linkplain java.lang.Thread#interrupt()* interrupted} by any thread before or while it is waiting, then an* {@code InterruptedException} is thrown.  This exception is not* thrown until the lock status of this object has been restored as* described above.** <p>* Note that the {@code wait} method, as it places the current thread* into the wait set for this object, unlocks only this object; any* other objects on which the current thread may be synchronized remain* locked while the thread waits.* <p>* This method should only be called by a thread that is the owner* of this object's monitor. See the {@code notify} method for a* description of the ways in which a thread can become the owner of* a monitor.** @param      timeout   the maximum time to wait in milliseconds.* @throws  IllegalArgumentException      if the value of timeout is*               negative.* @throws  IllegalMonitorStateException  if the current thread is not*               the owner of the object's monitor.* @throws  InterruptedException if any thread interrupted the*             current thread before or while the current thread*             was waiting for a notification.  The <i>interrupted*             status</i> of the current thread is cleared when*             this exception is thrown.* @see        java.lang.Object#notify()* @see        java.lang.Object#notifyAll()*/public final native void wait(long timeout) throws InterruptedException;/*** Causes the current thread to wait until another thread invokes the* {@link java.lang.Object#notify()} method or the* {@link java.lang.Object#notifyAll()} method for this object, or* some other thread interrupts the current thread, or a certain* amount of real time has elapsed.* <p>* This method is similar to the {@code wait} method of one* argument, but it allows finer control over the amount of time to* wait for a notification before giving up. The amount of real time,* measured in nanoseconds, is given by:* <blockquote>* <pre>* 1000000*timeout+nanos</pre></blockquote>* <p>* In all other respects, this method does the same thing as the* method {@link #wait(long)} of one argument. In particular,* {@code wait(0, 0)} means the same thing as {@code wait(0)}.* <p>* The current thread must own this object's monitor. The thread* releases ownership of this monitor and waits until either of the* following two conditions has occurred:* <ul>* <li>Another thread notifies threads waiting on this object's monitor*     to wake up either through a call to the {@code notify} method*     or the {@code notifyAll} method.* <li>The timeout period, specified by {@code timeout}*     milliseconds plus {@code nanos} nanoseconds arguments, has*     elapsed.* </ul>* <p>* The thread then waits until it can re-obtain ownership of the* monitor and resumes execution.* <p>* As in the one argument version, interrupts and spurious wakeups are* possible, and this method should always be used in a loop:* <pre>*     synchronized (obj) {*         while (&lt;condition does not hold&gt;)*             obj.wait(timeout, nanos);*         ... // Perform action appropriate to condition*     }* </pre>* This method should only be called by a thread that is the owner* of this object's monitor. See the {@code notify} method for a* description of the ways in which a thread can become the owner of* a monitor.** @param      timeout   the maximum time to wait in milliseconds.* @param      nanos      additional time, in nanoseconds range*                       0-999999.* @throws  IllegalArgumentException      if the value of timeout is*                      negative or the value of nanos is*                      not in the range 0-999999.* @throws  IllegalMonitorStateException  if the current thread is not*               the owner of this object's monitor.* @throws  InterruptedException if any thread interrupted the*             current thread before or while the current thread*             was waiting for a notification.  The <i>interrupted*             status</i> of the current thread is cleared when*             this exception is thrown.*/public final void wait(long timeout, int nanos) throws InterruptedException {if (timeout < 0) {throw new IllegalArgumentException("timeout value is negative");}if (nanos < 0 || nanos > 999999) {throw new IllegalArgumentException("nanosecond timeout value out of range");}if (nanos > 0) {timeout++;}wait(timeout);}/*** Causes the current thread to wait until another thread invokes the* {@link java.lang.Object#notify()} method or the* {@link java.lang.Object#notifyAll()} method for this object.* In other words, this method behaves exactly as if it simply* performs the call {@code wait(0)}.* <p>* The current thread must own this object's monitor. The thread* releases ownership of this monitor and waits until another thread* notifies threads waiting on this object's monitor to wake up* either through a call to the {@code notify} method or the* {@code notifyAll} method. The thread then waits until it can* re-obtain ownership of the monitor and resumes execution.* <p>* As in the one argument version, interrupts and spurious wakeups are* possible, and this method should always be used in a loop:* <pre>*     synchronized (obj) {*         while (&lt;condition does not hold&gt;)*             obj.wait();*         ... // Perform action appropriate to condition*     }* </pre>* This method should only be called by a thread that is the owner* of this object's monitor. See the {@code notify} method for a* description of the ways in which a thread can become the owner of* a monitor.** @throws  IllegalMonitorStateException  if the current thread is not*               the owner of the object's monitor.* @throws  InterruptedException if any thread interrupted the*             current thread before or while the current thread*             was waiting for a notification.  The <i>interrupted*             status</i> of the current thread is cleared when*             this exception is thrown.* @see        java.lang.Object#notify()* @see        java.lang.Object#notifyAll()*/public final void wait() throws InterruptedException {wait(0);}/*** Called by the garbage collector on an object when garbage collection* determines that there are no more references to the object.* A subclass overrides the {@code finalize} method to dispose of* system resources or to perform other cleanup.* <p>* The general contract of {@code finalize} is that it is invoked* if and when the Java&trade; virtual* machine has determined that there is no longer any* means by which this object can be accessed by any thread that has* not yet died, except as a result of an action taken by the* finalization of some other object or class which is ready to be* finalized. The {@code finalize} method may take any action, including* making this object available again to other threads; the usual purpose* of {@code finalize}, however, is to perform cleanup actions before* the object is irrevocably discarded. For example, the finalize method* for an object that represents an input/output connection might perform* explicit I/O transactions to break the connection before the object is* permanently discarded.* <p>* The {@code finalize} method of class {@code Object} performs no* special action; it simply returns normally. Subclasses of* {@code Object} may override this definition.* <p>* The Java programming language does not guarantee which thread will* invoke the {@code finalize} method for any given object. It is* guaranteed, however, that the thread that invokes finalize will not* be holding any user-visible synchronization locks when finalize is* invoked. If an uncaught exception is thrown by the finalize method,* the exception is ignored and finalization of that object terminates.* <p>* After the {@code finalize} method has been invoked for an object, no* further action is taken until the Java virtual machine has again* determined that there is no longer any means by which this object can* be accessed by any thread that has not yet died, including possible* actions by other objects or classes which are ready to be finalized,* at which point the object may be discarded.* <p>* The {@code finalize} method is never invoked more than once by a Java* virtual machine for any given object.* <p>* Any exception thrown by the {@code finalize} method causes* the finalization of this object to be halted, but is otherwise* ignored.** @throws Throwable the {@code Exception} raised by this method* @see java.lang.ref.WeakReference* @see java.lang.ref.PhantomReference* @jls 12.6 Finalization of Class Instances*/// 与JVM垃圾回收机制有关protected void finalize() throws Throwable { }
}
查看全文
如若内容造成侵权/违法违规/事实不符,请联系编程学习网邮箱:809451989@qq.com进行投诉反馈,一经查实,立即删除!

相关文章

  1. 林林总总的密码安全设备(一)

    根据“私钥永远不出KEY”的定律,在实际密码应用中基本上都是使用硬件设备作为私钥证书的载体。今天介绍一下主流的几种安全设备和应用结合模式。 USB Key USB Key的中文大名是智能密码钥匙,它是一种USB接口的硬件设备,内置芯片,有一定的存储空间,可以存储证书和私钥。凡是…...

    2024/4/19 18:28:46
  2. tensorflow gpu版本 查看可用gpu ,指定 gpu ,禁用gpu方法

    安装gpu版本的tensorflowpip install tensorflow-gpu # 默认安装最新版 如果需要指定版本的话使用,如1.11.0 pip install tensorflow-gpu==1.11.0查看可用gpufrom tensorflow.python.client import device_lib print(device_lib.list_local_devices())我的输出结果如下[name: …...

    2024/4/18 14:58:36
  3. 静态联编、动态联编与虚函数

    静态联编:在编译阶段 就将函数的实现与函数的调用绑定起来 动态联编:在程序运行时 将函数的实现与函数的调用绑定起来 例如: #include<iostream> using namespace std; class base{public:print(){cout<<"this is bases print"<<endl;} }; //派…...

    2024/4/16 5:05:07
  4. springboot(21)- 整合持久层(2)- 整合MyBatis

    1 整合MyBatis1.1 依赖 <dependency><groupId>mysql</groupId><artifactId>mysql-connector-java</artifactId><scope>runtime</scope><version>5.1.49</version></dependency><dependency><groupId>…...

    2024/4/16 5:04:57
  5. Everything Is Generated In Equal Probability(HDU - 6595,概率期望)

    一.题目链接:HDU-6595二.题目大意:题目给定一个正整数N.在区间[1, N]中随机等概率地选取一个正整数n,然后随机等概率地生成一个长度为n的排列A,然后调用函数 CALCULATE(A).SUBSEQUENCE(A):随机生成一个序列A的子序列.CNTINVERSIONPAIRS(A):返回序列A的逆序对数.CALCULATE…...

    2024/4/16 5:05:02
  6. 《MySQL必知必会》学习之 第18章 全文搜索

    第18章 全文搜索搜索引擎:MyISAM支持全文本搜索(InnoDB不支持)使用LIKE关键字或者正则表达式要求MySQL匹配表中所有行,随着行数增加,会很耗时,且不容易明确匹配什么不匹配什么,例如指定一个词必须匹配,一个词必须不匹配且结果不够智能化,如不会区分单个匹配的行和多个匹配…...

    2024/4/20 9:28:10
  7. SpringBoot对多线程的集成及异步调用,ThreadPoolTaskExecutor类

    多线程的集成及异步调用配置多线程ThreadPoolTaskExecutor配置ThreadPoolTaskExecutor参数SpringBoot中的异步调用1:定义任务方法2:在启动类上添加@EnableAsync注解3:回到测试类中编写测试方法test,然后测试4:线程池监控带返回值方法的调用及结果获取:threadPool.submit(…...

    2024/4/16 5:04:47
  8. 面向对象编程三大特性(csharp)

    1.封装 2.继承 3.多态 不扯别的,看代码就好… using System; //程序的声明 namespace demo0709 {//类名class Program{//主程序的入口static void Main(string[] args){//多态性Transport transport = new Bus();transport.reduceSpeed();transport.increaseSpeed();Console.R…...

    2024/3/28 18:29:36
  9. 3 | Spatial-based GNN/convolution模型之 NN4G

    NN4G(Neural Network for Grapy) 本文介绍属于的Spatial-based GNN/convolution类型的NN4G模型输入层先embedding Aggregation(聚合):相连接的邻居feature相加乘以权重,最后加上自己上一层layer的feature,来update。(这里回答了NN4G的aggregation是怎么做的)注意:不同…...

    2024/3/28 18:29:35
  10. 6.14 c++

    1.类的实现 一般有2种,一种在类定义时完成对成员函数的定义,一种是在类外进行定义。 类外实现 函数类型+类名::函数名 代码短就定义在类内,类内默认为inline函数(内联函数) 2.类的成员 如果在类的定义中既不指定private,也不指定public,则系统就默认为是私有的。 被声…...

    2024/4/16 5:05:12
  11. npm 不是内部命令

    这里介绍的是通过nvm来安装node,这样可以随意切换node版本。当然,也可以去node官网下载直接安装 1、先nvm下载 点击下载,选择nvm-setup.zip(安装版) 2、如果电脑装了杀毒软件,先关掉,获取安装的时候有提示选择允许所有操作,安装目录可以自定义,也可以选择程序默认的 3、使…...

    2024/4/16 5:04:26
  12. python 绘制爱心

    代码 import matplotlib.pyplot as plt import numpy as npt = np.arange(0, 2*np.pi,0.01) x = 20 * np.sin(t) **3 y = 13 * np.cos(t) - 5 * np.cos(2*t) - 2 * np.cos(3*t) - np.cos(4*t) plt.plot(x,y,color=r) ax=plt.gca() ax.fill(x,y,r,0.3) plt.grid() plt.show()效果…...

    2024/4/16 5:04:57
  13. JAVA中的sleep方法和休眠的解除 以及一道题目

    JAVA中的sleep方法关于线程的sleep方法 static void sleep(long mills)1、静态方法 2、参数是毫秒 3、作用:让当前线程进入休眠状态(阻塞状态),放弃当前占有的CPU时间片,让给其它线程使用 4、Thread.sleep()方法,可以做到这种效果: 间隔特定的时间,去执行一段特定的代码…...

    2024/4/16 5:04:52
  14. 1094 谷歌的招聘 (20分) C++版4ms通过所有测试点

    喜欢我的文章,记得点赞+收藏+关注の,你的反馈就是我不断更新的动力!QQ/Wechat:235 40008 原题目链接:1094 谷歌的招聘 (20分) 解题思路: 1.从头开始截取k位字符 2.如果k位字符对应的整数是素数,则输出该素数,结束程序。 3.截到末尾还没有素数,则输出404。 更多注解写在…...

    2024/4/16 5:05:27
  15. Ableton Live Suite 10.1.15 WiN中文版宿主软件

    Ableton Live Suite 10.1.15 PC | 1.95GBAbleton Live Suite 10.1.15 为您提供了支持创作过程的新工具和功能,从制作和定型声音到编辑和定型音乐。使用Live的新设备创建更大胆的声音。通过大量的工作流程改进来保持发展。使用Push,可以使笔记本计算机与计算机的距离更远。使用…...

    2024/4/16 5:05:02
  16. 操作系统整理

    一、进程与线程 1、简单说说进程、线程以及它们的区别 进程: 是系统进行资源分配和调度的一个独立单位,是最小的资源管理单位。线程: 是进程的一个实体,是 CPU 调度和分派的基本单位,是最小的 CPU 执行单元。线程自己不拥有任何系统资源,但是它可以访问其隶属进程的全部资…...

    2024/4/19 20:10:27
  17. 哪位大佬可以帮忙解决一下

    ...

    2024/4/16 5:05:02
  18. Mybatis框架的基本知识

    Mybatis什么是框架概述JDBC的三个重要对象环境配置文件案例操作注解使用实现类实现 什么是框架 框架是一种半成品软件,就是一组组件,供你完成你的系统(形象的来说就是使用别人已经搭好的舞台,你来表演)。它是程序员在软件开发过程中的一套解决方案,不同的框架解决的问题可…...

    2024/4/16 5:05:53
  19. Redis面试核心原理与数据结构使用场景

    文章目录Redis单线程和高性能Redis单线程如何处理并发客户端连接常见5种数据结构String应用场景Hash应用场景List两个阻塞指令应用场景Set指令应用场景抽奖活动点赞,收藏,标签集合操作,微博微信关注功能模型微博微信关注功能模型购物网站商品筛选ZSET集合操作排行榜 Redis单…...

    2024/4/16 5:05:12
  20. Java面试——TCP与HTTP

    一、Session 和 cookie 的区别 【1】Cookie 保存在客户端,未设置存储时间的 Cookie,关闭浏览器会话 Cookie 就会被删除;设置了存储时间的 Cookie 保存在用户设备的磁盘中直到过期,同时 Cookie 在客户端所以可以伪造,不是十分安全,敏感数据不易保存。Session 保存在服务器…...

    2024/4/16 5:05:58

最新文章

  1. 协方差和协相关(Covariance and Correlation)

    本文主要是记录与这两个概念相关的概念。看中文或者英文时&#xff0c;尝尝容易弄混。 内容 1 covariance和correleation2 covariance matrix和correlation matrix3 cross-covariance和cross-correlation4 autocovariance和autocorrelation 对于两个随机信号X, Y 1 covarianc…...

    2024/4/20 21:00:19
  2. 梯度消失和梯度爆炸的一些处理方法

    在这里是记录一下梯度消失或梯度爆炸的一些处理技巧。全当学习总结了如有错误还请留言&#xff0c;在此感激不尽。 权重和梯度的更新公式如下&#xff1a; w w − η ⋅ ∇ w w w - \eta \cdot \nabla w ww−η⋅∇w 个人通俗的理解梯度消失就是网络模型在反向求导的时候出…...

    2024/3/20 10:50:27
  3. 将.docx格式文件转成html,uniapp使用u-parse展示

    使用mammoth。 1、在index.html中加入&#xff1a; <!DOCTYPE html> <html lang"en"><head><meta charset"UTF-8" /><meta http-equiv"X-UA-Compatible" content"IEedge" /><meta name"viewp…...

    2024/4/18 23:28:43
  4. OpenCV单通道图像按像素成倍比例放大(无高斯平滑处理)

    OpenCV中的resize函数可以对图像做任意比例的放大(/缩小)处理&#xff0c;该处理过程会对图像做高斯模糊化以保证图像在进行放大&#xff08;/缩小&#xff09;后尽可能保留源图像所展现的具体内容&#xff08;消除固定频率插值/采样带来的香农采样信息损失&#xff09;&#x…...

    2024/4/18 9:35:54
  5. 第十一届蓝桥杯物联网试题(省赛)

    对于通信方面&#xff0c;还是终端A、B都保持接收状态&#xff0c;当要发送的数组不为空再发送数据&#xff0c;发送完后立即清除&#xff0c;接收数据的数组不为空则处理&#xff0c;处理完后立即清除&#xff0c;分工明确 继电器不亮一般可能是电压不够 将数据加空格再加\r…...

    2024/4/19 13:28:03
  6. 【外汇早评】美通胀数据走低,美元调整

    原标题:【外汇早评】美通胀数据走低,美元调整昨日美国方面公布了新一期的核心PCE物价指数数据,同比增长1.6%,低于前值和预期值的1.7%,距离美联储的通胀目标2%继续走低,通胀压力较低,且此前美国一季度GDP初值中的消费部分下滑明显,因此市场对美联储后续更可能降息的政策…...

    2024/4/19 14:24:02
  7. 【原油贵金属周评】原油多头拥挤,价格调整

    原标题:【原油贵金属周评】原油多头拥挤,价格调整本周国际劳动节,我们喜迎四天假期,但是整个金融市场确实流动性充沛,大事频发,各个商品波动剧烈。美国方面,在本周四凌晨公布5月份的利率决议和新闻发布会,维持联邦基金利率在2.25%-2.50%不变,符合市场预期。同时美联储…...

    2024/4/19 18:20:22
  8. 【外汇周评】靓丽非农不及疲软通胀影响

    原标题:【外汇周评】靓丽非农不及疲软通胀影响在刚结束的周五,美国方面公布了新一期的非农就业数据,大幅好于前值和预期,新增就业重新回到20万以上。具体数据: 美国4月非农就业人口变动 26.3万人,预期 19万人,前值 19.6万人。 美国4月失业率 3.6%,预期 3.8%,前值 3…...

    2024/4/19 11:57:31
  9. 【原油贵金属早评】库存继续增加,油价收跌

    原标题:【原油贵金属早评】库存继续增加,油价收跌周三清晨公布美国当周API原油库存数据,上周原油库存增加281万桶至4.692亿桶,增幅超过预期的74.4万桶。且有消息人士称,沙特阿美据悉将于6月向亚洲炼油厂额外出售更多原油,印度炼油商预计将每日获得至多20万桶的额外原油供…...

    2024/4/19 11:57:31
  10. 【外汇早评】日本央行会议纪要不改日元强势

    原标题:【外汇早评】日本央行会议纪要不改日元强势近两日日元大幅走强与近期市场风险情绪上升,避险资金回流日元有关,也与前一段时间的美日贸易谈判给日本缓冲期,日本方面对汇率问题也避免继续贬值有关。虽然今日早间日本央行公布的利率会议纪要仍然是支持宽松政策,但这符…...

    2024/4/19 11:57:52
  11. 【原油贵金属早评】欧佩克稳定市场,填补伊朗问题的影响

    原标题:【原油贵金属早评】欧佩克稳定市场,填补伊朗问题的影响近日伊朗局势升温,导致市场担忧影响原油供给,油价试图反弹。此时OPEC表态稳定市场。据消息人士透露,沙特6月石油出口料将低于700万桶/日,沙特已经收到石油消费国提出的6月份扩大出口的“适度要求”,沙特将满…...

    2024/4/19 11:57:53
  12. 【外汇早评】美欲与伊朗重谈协议

    原标题:【外汇早评】美欲与伊朗重谈协议美国对伊朗的制裁遭到伊朗的抗议,昨日伊朗方面提出将部分退出伊核协议。而此行为又遭到欧洲方面对伊朗的谴责和警告,伊朗外长昨日回应称,欧洲国家履行它们的义务,伊核协议就能保证存续。据传闻伊朗的导弹已经对准了以色列和美国的航…...

    2024/4/19 11:58:14
  13. 【原油贵金属早评】波动率飙升,市场情绪动荡

    原标题:【原油贵金属早评】波动率飙升,市场情绪动荡因中美贸易谈判不安情绪影响,金融市场各资产品种出现明显的波动。随着美国与中方开启第十一轮谈判之际,美国按照既定计划向中国2000亿商品征收25%的关税,市场情绪有所平复,已经开始接受这一事实。虽然波动率-恐慌指数VI…...

    2024/4/19 11:58:20
  14. 【原油贵金属周评】伊朗局势升温,黄金多头跃跃欲试

    原标题:【原油贵金属周评】伊朗局势升温,黄金多头跃跃欲试美国和伊朗的局势继续升温,市场风险情绪上升,避险黄金有向上突破阻力的迹象。原油方面稍显平稳,近期美国和OPEC加大供给及市场需求回落的影响,伊朗局势并未推升油价走强。近期中美贸易谈判摩擦再度升级,美国对中…...

    2024/4/20 7:40:48
  15. 【原油贵金属早评】市场情绪继续恶化,黄金上破

    原标题:【原油贵金属早评】市场情绪继续恶化,黄金上破周初中国针对于美国加征关税的进行的反制措施引发市场情绪的大幅波动,人民币汇率出现大幅的贬值动能,金融市场受到非常明显的冲击。尤其是波动率起来之后,对于股市的表现尤其不安。隔夜美国股市出现明显的下行走势,这…...

    2024/4/19 11:58:39
  16. 【外汇早评】美伊僵持,风险情绪继续升温

    原标题:【外汇早评】美伊僵持,风险情绪继续升温昨日沙特两艘油轮再次发生爆炸事件,导致波斯湾局势进一步恶化,市场担忧美伊可能会出现摩擦生火,避险品种获得支撑,黄金和日元大幅走强。美指受中美贸易问题影响而在低位震荡。继5月12日,四艘商船在阿联酋领海附近的阿曼湾、…...

    2024/4/19 11:58:51
  17. 【原油贵金属早评】贸易冲突导致需求低迷,油价弱势

    原标题:【原油贵金属早评】贸易冲突导致需求低迷,油价弱势近日虽然伊朗局势升温,中东地区几起油船被袭击事件影响,但油价并未走高,而是出于调整结构中。由于市场预期局势失控的可能性较低,而中美贸易问题导致的全球经济衰退风险更大,需求会持续低迷,因此油价调整压力较…...

    2024/4/20 3:12:02
  18. 氧生福地 玩美北湖(上)——为时光守候两千年

    原标题:氧生福地 玩美北湖(上)——为时光守候两千年一次说走就走的旅行,只有一张高铁票的距离~ 所以,湖南郴州,我来了~ 从广州南站出发,一个半小时就到达郴州西站了。在动车上,同时改票的南风兄和我居然被分到了一个车厢,所以一路非常愉快地聊了过来。 挺好,最起…...

    2024/4/19 11:59:15
  19. 氧生福地 玩美北湖(中)——永春梯田里的美与鲜

    原标题:氧生福地 玩美北湖(中)——永春梯田里的美与鲜一觉醒来,因为大家太爱“美”照,在柳毅山庄去寻找龙女而错过了早餐时间。近十点,向导坏坏还是带着饥肠辘辘的我们去吃郴州最富有盛名的“鱼头粉”。说这是“十二分推荐”,到郴州必吃的美食之一。 哇塞!那个味美香甜…...

    2024/4/19 11:59:23
  20. 氧生福地 玩美北湖(下)——奔跑吧骚年!

    原标题:氧生福地 玩美北湖(下)——奔跑吧骚年!让我们红尘做伴 活得潇潇洒洒 策马奔腾共享人世繁华 对酒当歌唱出心中喜悦 轰轰烈烈把握青春年华 让我们红尘做伴 活得潇潇洒洒 策马奔腾共享人世繁华 对酒当歌唱出心中喜悦 轰轰烈烈把握青春年华 啊……啊……啊 两…...

    2024/4/19 11:59:44
  21. 扒开伪装医用面膜,翻六倍价格宰客,小姐姐注意了!

    原标题:扒开伪装医用面膜,翻六倍价格宰客,小姐姐注意了!扒开伪装医用面膜,翻六倍价格宰客!当行业里的某一品项火爆了,就会有很多商家蹭热度,装逼忽悠,最近火爆朋友圈的医用面膜,被沾上了污点,到底怎么回事呢? “比普通面膜安全、效果好!痘痘、痘印、敏感肌都能用…...

    2024/4/19 11:59:48
  22. 「发现」铁皮石斛仙草之神奇功效用于医用面膜

    原标题:「发现」铁皮石斛仙草之神奇功效用于医用面膜丽彦妆铁皮石斛医用面膜|石斛多糖无菌修护补水贴19大优势: 1、铁皮石斛:自唐宋以来,一直被列为皇室贡品,铁皮石斛生于海拔1600米的悬崖峭壁之上,繁殖力差,产量极低,所以古代仅供皇室、贵族享用 2、铁皮石斛自古民间…...

    2024/4/19 12:00:06
  23. 丽彦妆\医用面膜\冷敷贴轻奢医学护肤引导者

    原标题:丽彦妆\医用面膜\冷敷贴轻奢医学护肤引导者【公司简介】 广州华彬企业隶属香港华彬集团有限公司,专注美业21年,其旗下品牌: 「圣茵美」私密荷尔蒙抗衰,产后修复 「圣仪轩」私密荷尔蒙抗衰,产后修复 「花茵莳」私密荷尔蒙抗衰,产后修复 「丽彦妆」专注医学护…...

    2024/4/19 16:57:22
  24. 广州械字号面膜生产厂家OEM/ODM4项须知!

    原标题:广州械字号面膜生产厂家OEM/ODM4项须知!广州械字号面膜生产厂家OEM/ODM流程及注意事项解读: 械字号医用面膜,其实在我国并没有严格的定义,通常我们说的医美面膜指的应该是一种「医用敷料」,也就是说,医用面膜其实算作「医疗器械」的一种,又称「医用冷敷贴」。 …...

    2024/4/19 12:00:25
  25. 械字号医用眼膜缓解用眼过度到底有无作用?

    原标题:械字号医用眼膜缓解用眼过度到底有无作用?医用眼膜/械字号眼膜/医用冷敷眼贴 凝胶层为亲水高分子材料,含70%以上的水分。体表皮肤温度传导到本产品的凝胶层,热量被凝胶内水分子吸收,通过水分的蒸发带走大量的热量,可迅速地降低体表皮肤局部温度,减轻局部皮肤的灼…...

    2024/4/19 12:00:40
  26. 配置失败还原请勿关闭计算机,电脑开机屏幕上面显示,配置失败还原更改 请勿关闭计算机 开不了机 这个问题怎么办...

    解析如下&#xff1a;1、长按电脑电源键直至关机&#xff0c;然后再按一次电源健重启电脑&#xff0c;按F8健进入安全模式2、安全模式下进入Windows系统桌面后&#xff0c;按住“winR”打开运行窗口&#xff0c;输入“services.msc”打开服务设置3、在服务界面&#xff0c;选中…...

    2022/11/19 21:17:18
  27. 错误使用 reshape要执行 RESHAPE,请勿更改元素数目。

    %读入6幅图像&#xff08;每一幅图像的大小是564*564&#xff09; f1 imread(WashingtonDC_Band1_564.tif); subplot(3,2,1),imshow(f1); f2 imread(WashingtonDC_Band2_564.tif); subplot(3,2,2),imshow(f2); f3 imread(WashingtonDC_Band3_564.tif); subplot(3,2,3),imsho…...

    2022/11/19 21:17:16
  28. 配置 已完成 请勿关闭计算机,win7系统关机提示“配置Windows Update已完成30%请勿关闭计算机...

    win7系统关机提示“配置Windows Update已完成30%请勿关闭计算机”问题的解决方法在win7系统关机时如果有升级系统的或者其他需要会直接进入一个 等待界面&#xff0c;在等待界面中我们需要等待操作结束才能关机&#xff0c;虽然这比较麻烦&#xff0c;但是对系统进行配置和升级…...

    2022/11/19 21:17:15
  29. 台式电脑显示配置100%请勿关闭计算机,“准备配置windows 请勿关闭计算机”的解决方法...

    有不少用户在重装Win7系统或更新系统后会遇到“准备配置windows&#xff0c;请勿关闭计算机”的提示&#xff0c;要过很久才能进入系统&#xff0c;有的用户甚至几个小时也无法进入&#xff0c;下面就教大家这个问题的解决方法。第一种方法&#xff1a;我们首先在左下角的“开始…...

    2022/11/19 21:17:14
  30. win7 正在配置 请勿关闭计算机,怎么办Win7开机显示正在配置Windows Update请勿关机...

    置信有很多用户都跟小编一样遇到过这样的问题&#xff0c;电脑时发现开机屏幕显现“正在配置Windows Update&#xff0c;请勿关机”(如下图所示)&#xff0c;而且还需求等大约5分钟才干进入系统。这是怎样回事呢&#xff1f;一切都是正常操作的&#xff0c;为什么开时机呈现“正…...

    2022/11/19 21:17:13
  31. 准备配置windows 请勿关闭计算机 蓝屏,Win7开机总是出现提示“配置Windows请勿关机”...

    Win7系统开机启动时总是出现“配置Windows请勿关机”的提示&#xff0c;没过几秒后电脑自动重启&#xff0c;每次开机都这样无法进入系统&#xff0c;此时碰到这种现象的用户就可以使用以下5种方法解决问题。方法一&#xff1a;开机按下F8&#xff0c;在出现的Windows高级启动选…...

    2022/11/19 21:17:12
  32. 准备windows请勿关闭计算机要多久,windows10系统提示正在准备windows请勿关闭计算机怎么办...

    有不少windows10系统用户反映说碰到这样一个情况&#xff0c;就是电脑提示正在准备windows请勿关闭计算机&#xff0c;碰到这样的问题该怎么解决呢&#xff0c;现在小编就给大家分享一下windows10系统提示正在准备windows请勿关闭计算机的具体第一种方法&#xff1a;1、2、依次…...

    2022/11/19 21:17:11
  33. 配置 已完成 请勿关闭计算机,win7系统关机提示“配置Windows Update已完成30%请勿关闭计算机”的解决方法...

    今天和大家分享一下win7系统重装了Win7旗舰版系统后&#xff0c;每次关机的时候桌面上都会显示一个“配置Windows Update的界面&#xff0c;提示请勿关闭计算机”&#xff0c;每次停留好几分钟才能正常关机&#xff0c;导致什么情况引起的呢&#xff1f;出现配置Windows Update…...

    2022/11/19 21:17:10
  34. 电脑桌面一直是清理请关闭计算机,windows7一直卡在清理 请勿关闭计算机-win7清理请勿关机,win7配置更新35%不动...

    只能是等着&#xff0c;别无他法。说是卡着如果你看硬盘灯应该在读写。如果从 Win 10 无法正常回滚&#xff0c;只能是考虑备份数据后重装系统了。解决来方案一&#xff1a;管理员运行cmd&#xff1a;net stop WuAuServcd %windir%ren SoftwareDistribution SDoldnet start WuA…...

    2022/11/19 21:17:09
  35. 计算机配置更新不起,电脑提示“配置Windows Update请勿关闭计算机”怎么办?

    原标题&#xff1a;电脑提示“配置Windows Update请勿关闭计算机”怎么办&#xff1f;win7系统中在开机与关闭的时候总是显示“配置windows update请勿关闭计算机”相信有不少朋友都曾遇到过一次两次还能忍但经常遇到就叫人感到心烦了遇到这种问题怎么办呢&#xff1f;一般的方…...

    2022/11/19 21:17:08
  36. 计算机正在配置无法关机,关机提示 windows7 正在配置windows 请勿关闭计算机 ,然后等了一晚上也没有关掉。现在电脑无法正常关机...

    关机提示 windows7 正在配置windows 请勿关闭计算机 &#xff0c;然后等了一晚上也没有关掉。现在电脑无法正常关机以下文字资料是由(历史新知网www.lishixinzhi.com)小编为大家搜集整理后发布的内容&#xff0c;让我们赶快一起来看一下吧&#xff01;关机提示 windows7 正在配…...

    2022/11/19 21:17:05
  37. 钉钉提示请勿通过开发者调试模式_钉钉请勿通过开发者调试模式是真的吗好不好用...

    钉钉请勿通过开发者调试模式是真的吗好不好用 更新时间:2020-04-20 22:24:19 浏览次数:729次 区域: 南阳 > 卧龙 列举网提醒您:为保障您的权益,请不要提前支付任何费用! 虚拟位置外设器!!轨迹模拟&虚拟位置外设神器 专业用于:钉钉,外勤365,红圈通,企业微信和…...

    2022/11/19 21:17:05
  38. 配置失败还原请勿关闭计算机怎么办,win7系统出现“配置windows update失败 还原更改 请勿关闭计算机”,长时间没反应,无法进入系统的解决方案...

    前几天班里有位学生电脑(windows 7系统)出问题了&#xff0c;具体表现是开机时一直停留在“配置windows update失败 还原更改 请勿关闭计算机”这个界面&#xff0c;长时间没反应&#xff0c;无法进入系统。这个问题原来帮其他同学也解决过&#xff0c;网上搜了不少资料&#x…...

    2022/11/19 21:17:04
  39. 一个电脑无法关闭计算机你应该怎么办,电脑显示“清理请勿关闭计算机”怎么办?...

    本文为你提供了3个有效解决电脑显示“清理请勿关闭计算机”问题的方法&#xff0c;并在最后教给你1种保护系统安全的好方法&#xff0c;一起来看看&#xff01;电脑出现“清理请勿关闭计算机”在Windows 7(SP1)和Windows Server 2008 R2 SP1中&#xff0c;添加了1个新功能在“磁…...

    2022/11/19 21:17:03
  40. 请勿关闭计算机还原更改要多久,电脑显示:配置windows更新失败,正在还原更改,请勿关闭计算机怎么办...

    许多用户在长期不使用电脑的时候&#xff0c;开启电脑发现电脑显示&#xff1a;配置windows更新失败&#xff0c;正在还原更改&#xff0c;请勿关闭计算机。。.这要怎么办呢&#xff1f;下面小编就带着大家一起看看吧&#xff01;如果能够正常进入系统&#xff0c;建议您暂时移…...

    2022/11/19 21:17:02
  41. 还原更改请勿关闭计算机 要多久,配置windows update失败 还原更改 请勿关闭计算机,电脑开机后一直显示以...

    配置windows update失败 还原更改 请勿关闭计算机&#xff0c;电脑开机后一直显示以以下文字资料是由(历史新知网www.lishixinzhi.com)小编为大家搜集整理后发布的内容&#xff0c;让我们赶快一起来看一下吧&#xff01;配置windows update失败 还原更改 请勿关闭计算机&#x…...

    2022/11/19 21:17:01
  42. 电脑配置中请勿关闭计算机怎么办,准备配置windows请勿关闭计算机一直显示怎么办【图解】...

    不知道大家有没有遇到过这样的一个问题&#xff0c;就是我们的win7系统在关机的时候&#xff0c;总是喜欢显示“准备配置windows&#xff0c;请勿关机”这样的一个页面&#xff0c;没有什么大碍&#xff0c;但是如果一直等着的话就要两个小时甚至更久都关不了机&#xff0c;非常…...

    2022/11/19 21:17:00
  43. 正在准备配置请勿关闭计算机,正在准备配置windows请勿关闭计算机时间长了解决教程...

    当电脑出现正在准备配置windows请勿关闭计算机时&#xff0c;一般是您正对windows进行升级&#xff0c;但是这个要是长时间没有反应&#xff0c;我们不能再傻等下去了。可能是电脑出了别的问题了&#xff0c;来看看教程的说法。正在准备配置windows请勿关闭计算机时间长了方法一…...

    2022/11/19 21:16:59
  44. 配置失败还原请勿关闭计算机,配置Windows Update失败,还原更改请勿关闭计算机...

    我们使用电脑的过程中有时会遇到这种情况&#xff0c;当我们打开电脑之后&#xff0c;发现一直停留在一个界面&#xff1a;“配置Windows Update失败&#xff0c;还原更改请勿关闭计算机”&#xff0c;等了许久还是无法进入系统。如果我们遇到此类问题应该如何解决呢&#xff0…...

    2022/11/19 21:16:58
  45. 如何在iPhone上关闭“请勿打扰”

    Apple’s “Do Not Disturb While Driving” is a potentially lifesaving iPhone feature, but it doesn’t always turn on automatically at the appropriate time. For example, you might be a passenger in a moving car, but your iPhone may think you’re the one dri…...

    2022/11/19 21:16:57