Is assert a keyword?

Hi,
Since Assertions are new addition to ver 1.4, can "assert" be treated as a new keyword? I could not find this anywhere else even in the Java Docs. Can someone please clarify?
Thanks,
Venkat Dhurjati

Thanks for your answer. My question is can we include the word "assert" in Java list of keywords. ie., just like "abstract" is a keyword, is "assert" also a keyword?
- Venkat

Similar Messages

Assert keyword reference in javafx

I've been looking for a javafx webpage that will get me
the list of keywords in javafx 1.2. However, this link:
http://openjfx.java.sun.com/current-build/doc/reference/JavaFXReference.html
doesn't seem to work anymore. I did find this one:
http://jarfiller.com/reference/javafxscript/
Which has a full page of examples on how to use the keyword assert.
So I tried this in netbeans:
package javafxapplication19;
assert(true);
But this will not compile either with Netbeans 6.8 or javafxc 1.2.3.
Question is where can I get a list of javafx keywords on the net?
And what am I doing wrong with my simple javafx program?
Tom

Ah, openjfx is back up. The [language reference|http://openjfx.java.sun.com/current-build/doc/reference/apas01.html] has this list of reserved words:
{noformat}abstract after and as assert at attribute before bind bound break{noformat}
{noformat}catch class continue def delete else exclusive extends false finally{noformat}
{noformat}first for from function if import indexof in init insert instanceof into{noformat}
{noformat}inverse last lazy mixin mod new not null on or override package{noformat}
{noformat}postinit private protected public-init public public-read replace return{noformat}
{noformat}reverse sizeof static step super then this throw trigger true try tween{noformat}
{noformat}typeof var where while with{noformat}
Hm, seems somewhat out of date.
Good point about the difference between "reserved words" and keywords that are
not reserved. I didn't know about this. However, the file {color:#ff00ff}v4Parser.g{color} right
next to the file {color:#ff00ff}v4Lexer.g{color} I referenced above has a nice explanation of
the difference between reserved words and non-reserved keywords. As usual, the
source code seems to be the definitive documentation.
Note, you can still use the double angle bracket syntax to use even reserved words as identifiers,
for example, {color:#ff00ff}var <<typeof>> = 1{color}. Why anyone would want to do this, I'm not sure.
I still don't know what {color:#ff00ff}typeof{color} does. Yes, {color:#ff00ff}invalidate{color} was added after 1.2. I'm
not sure what its status is though. Not that I'm trying to keep secrets. If it's merely
experimental, though, I wouldn't want to encourage people to use it. Sufficiently motivated
individuals are welcome to look through the source code. :-)
Edited by: smarks on Apr 6, 2010 11:15 AM

Assert keyword?

I'm trying to implement some code that I found in a book, and they use "assert", but when I try to compile with NetBeans 3.6, I get a warning that says,
"warning, as of Java 1.4, assert is a keyword, and may not used as an identifiier"
here's an example of the way it is used in the program:
while ((u = extractMin()) != null)
            assert !isSettled(u);
        }can someone help me out with how I would write that statement a different way, without using "assert"?
Thanks!

Actually, it looks like you are using a true assertion, rather than trying to use assert as a identifier.
Take a look at the following web-page.
http://java.sun.com/j2se/1.4.2/docs/guide/lang/assert.htmlIt will tell you how to compile using assertions, which, I believe, is turned off by default.
� {�

Assertion Failed - Dump when clicking on the links from Portal for WD Comp

Hi,
We have a WD Component which is integrated to the Portal . When we click on the link in the Portal for the first 2 times, the selection screen is shown correctly ( when debugged, the program stops in WDDOINIT method before the sel.screen is shown).
When we click on the link for the third or fourth time with no time gap, it shows a dump. This is the dump I am getting.
Runtime Errors         ASSERTION_FAILED
Date and Time          01/06/2011 10:13:58
Short text
The ASSERT condition was violated.
What happened?
In the running application program, the ASSERT statement recognized a
situation that should not have occurred.
The runtime error was triggered for one of these reasons:
- For the checkpoint group specified with the ASSERT statement, the
activation mode is set to "abort".
- Via a system variant, the activation mode is globally set to "abort"
for checkpoint groups in this system.
- The activation mode is set to "abort" on program level.
- The ASSERT statement is not assigned to any checkpoint group.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"ASSERTION_FAILED" " "
"CL_NW7_VIEW_ELEMENT_ADAPTER===CP" or "CL_NW7_VIEW_ELEMENT_ADAPTER===CM004"
"DISPATCH_NW7_EVENT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
User and Transaction
Client.............. 010
User................ "STECURRY"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "4D250E9ADDFB00BDE10080000A041004"
Program............. "CL_NW7_VIEW_ELEMENT_ADAPTER===CP"
Screen.............. "SAPMHTTP 0010"
Screen Line......... 2
Information on Caller ofr "HTTPS" Connection:
Plug-in Type.......... "HTTPS"
Caller IP............. "10.6.4.220"
Caller Port........... 443
Universal Resource Id. "/sap/bc/webdynpro/sap/ZEM_INV_APP_ASSIGNMENTS/"
Information on where terminated
Termination occurred in the ABAP program "CL_NW7_VIEW_ELEMENT_ADAPTER===CP" -
in "DISPATCH_NW7_EVENT".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 5
of the (Include) program "CL_NW7_VIEW_ELEMENT_ADAPTER===CM004".
Source Code Extract
Line
SourceCde
1
METHOD dispatch_nw7_event.
2
DATA: l_event_handler TYPE REF TO if_wdr_nw7_event_handler.
3
4
l_event_handler = get_nw7_event_handler( i_event_handler_id ).
>>>>>
assert l_event_handler is not initial.
6
7
" View-based Delta Rendering: tracking of client events
8
raise event on_nw7_handle_event
9
exporting
10
event_handler = l_event_handler
11
event_name    = i_event_name.
12
13
14
l_event_handler->handle_event(
15
i_event_name       = i_event_name
16
i_event_parameters = i_event_parameters
17
i_update_data      = i_update_data
18
i_event_queue      = i_event_queue ).
19
ENDMETHOD.
- I have cut the dump to make it short and clear.
One of my colleague ran a HTTP watch trace and I am attaching it as well.
<body> <table cellpadding="0" cellspacing="0" border="0" width="100%"> <tr> <td> <h1> Error when processing your request </h1> <br> <h2> What has happened? </h2> <p> The URL https://uswasspq.deloitte.com:/sap/bc/webdynpro/sap/ZEM_INV_APPROVER_MAIN//ucfLOADING was not called due to an error. </p> </td> </tr> <tr> <td> </td> </tr> <tr> <td class="emphasize"> <strong> Note </strong> <br> <ul> <li> The following error text was processed in the system SPQ : <b> User session (HTTP/SMTP/..) closed after timeout </b> </li> </ul> <ul> <li> The error occurred on the application server usuxc204_SPQ_01 and in the work process 1 . </li> </ul> <ul> <li> The termination type was: ERROR_MESSAGE_STATE </li> </ul> <ul> <li> The ABAP call stack was: <br> Method: PREPROCESS_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP<BR>Method: IF_HTTP_EXTENSIONHANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP<BR>Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP<BR>Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME<BR>Module: %_HTTP_START of program SAPMHTTP<BR> </li> </ul> </td> </tr> <tr> <td> </td> </tr> <tr> <td> <p> </p> <h2> What can I do? </h2> <ul> <li> If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SPQ in transaction ST22. </li> </ul> <ul> <li> If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server usuxc204_SPQ_01 in transaction SM21. </li> </ul> <ul> <li> If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server usuxc204_SPQ_01 . In some situations, you may also need to analyze the trace files of other work processes. </li> </ul> <ul> <li> If you do not yet have a user ID, contact your system administrator. </li> </ul> <br/> <p class="note"> Error code: ICF-IE-https -c: 010 -u: STHUGHES -l: E -s: SPQ -i: usuxc204_SPQ_01 -w: 1 -d: 20110208 -t: 131808 -v: ERROR_MESSAGE_STATE -e: User session (HTTP/SMTP/..) closed after timeout </p> <br/> <p> HTTP 500 - Internal Server Error <br/> <p> Your SAP Internet Communication Framework Team </p> </td> </tr> </table> </body> </html>
After this error a URL is called form the WebDynpro to the following html page.
https://uswasspq.deloitte.com/sap/bc/webdynpro/sap/zem_inv_approver_main/dps_Error_Page.html ( this is the friendly message we have put so that the user does not see the dump on his screen.
I tried invalidating the nodes in the WDDOEXIT at the view level but it did not help. This is a show stopper for the project to go live.
Thanks,
Guru.

Hi Guru,
It is not readable the way you posted and that might be the reason that you do not get reactions.
Can you please confirm the following.
1. Is this problem occurs with out portal when you run the application standalone in SAP GUI.
2. What is going on wddoinit method or wddomodify method, any resource handling there ?

Assertions in JDeveloper

There seems to be a bug in JDeveloper regarding assertions. I have configured it to use JDK 1.4, enabled assertions in the IDE and set the target to 1.4. I also uncommented the line in jdev.conf that makes the editor recognize assert as a keyword. But when I try to compile a java class containing assertions, I get one of two errors:
1) If the assertion will always succeed, I get an internal compiler error. For example
assert 1 < 2;
2) Otherwise I get this error message
Error(35,10): constructor AssertionError(<anything>) not found in class java.lang.AssertionError
What can I do?
Knut Støre

I forgot to say that the last error message is the same whether I add a message or not.
assert x != null : "Something is wrong";
or
assert x != null;

How to use assert with wireless toolkit?

Hi,
I am trying to find out how to use assert with wireless toolkit. I have found that I need to pass "-source 1.4" to the java compiler. But I can't find any documentation on how to do it.
I'm using J2ME Wireless Toolkit 2.2.
thanks
Ludde

Here's a quote from an article on Java World at http://www.javaworld.com/javaworld/jw-11-2001/jw-1109-assert.html
"To support the new assertion facility in J2SE 1.4, the Java platform adds the keyword assert to the language, an AssertionError class, and a few additional methods to java.lang.ClassLoader."
So I really think it's part of 1.4.

Assert error!! how to solve that problem?

Hi,
when i use an assert after the compilation , the error is:
C:\CLASSES>javac Assertion.java
Assertion.java:11: as of release 1.4, 'assert' is a keyword, and may not be used as an identifier
(try -source 1.3 or lower to use 'assert' as an identifier)
public static void assert(boolean expression, String why) {
^
1 error
The tutorial says: In order for Code Sample 1(Doesn't matter) to compile, use -source 1.3 because assert is a keyword as of J2SE 1.4.
what is the source 1.3 ?? where and what the hell is that?? LOL =))
thanks!

i understand and i don't understand.
lol
thats possible for someone who is using xemacs but someone who is using Eclipse or JCreator how do i do that?
if u don't want to answer that question could u put an assertion in this code, for example : asser -> if the num < = 0 !
here is the code:
import java.io.*;
public class Capicua {
     public static void main (String[] args) throws Exception {
          int digit, num;
          int inverted = 0;
          int x;
               BufferedReader br = new BufferedReader(new InputStreamReader(System.in));
               System.out.print(" Insert number: ");
               num=Integer.parseInt(br.readLine().trim());
               Assertion.assert(num <= 0, "Number can't be shorter or equals to zero!"); <--- how do i put an assert here? ( with the "do - while" its easy, but and with the asserts?
               x=num;
               while(num > 0) {
               digit = num % 10;
               num = num /10;
               inverted = inverted * 10 + digit;
               System.out.println("inverted = " + inverted);
                    if(inverted == x) {
                         System.out.println("Capicua");
                    }else{
                         System.out.println("not a capicau");
}

How to Use " ASSERT ID " , in the programm and what is the use of it?

Hi,
friends,
I wanted to write a program (TEST CASE) by using ASSERT ID . But i got the description (Hint) like what iam mentioning below:
*" Detects uses of ASSERT ID and flags cases where there is code to be executed after the command. In production environments ASSERTS are disabled, as a rule, therefore this code gets to be executed. "
So, let me know the Use of this key word with some example .
Thanks & Regards,
P.N.Kumar

Hi,
     Please look for F1 on this keyword. Also look at "Checkpoints".
     Check this link.
     http://help.sap.com/erp2005_ehp_02/helpdata/EN/9b/b1b64104e52f31e10000000a155106/frameset.htm
Regards,
Srini.

Assertion failed Dump in ALV

Hello,
I am displaying a ALV report as POP-UP . Its developed based on OOPS ( gr_table->Display).
The ALV displaying the output perfectly when the records are less. For example, the ALV pop-up able to show the 50 records perfectly . If the records are more than 50 (example 500), then i have to scroll down to see the records from 51 to 500. When the records are high , the Alv trying to display the output.. but in a second, its throwing the dump((ASSERTION_FAILED)). Few times, its able to display the data, when i am trying to scroll down to see the below records..its throwing the dump (ASSERTION_FAILED). I tried with all possibilities but no luck. And no idea about ASSERTION FAILED DUMP.
Kindly help.
Regards,
Venkat

Hello Both,
Thanks for the reply. Please find the error details
The ASSERT condition was violated.
Error analysis
    The following checkpoint group was used: "No checkpoint group specified"
    If in the ASSERT statement the addition FIELDS was used, you can find
    the content of the first 8 specified fields in the following overview:
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"ASSERTION_FAILED" " "
"CL_DATAPTABLECACHE============CP" or "CL_DATAPTABLECACHE============CM00P"
"TRANSMIT_PACKET"
Any clue. Please.
Venkat

Assertions in jbuilder7

hey all,
i seem to not be able to get assertions to work in jbuilder7. Dunno if my ide ia relevant but i cant find the error in my code so im assuming its got something to do with my ide?
anwayz i have this
private boolean checkState(){
boolean check = getState();
//check the class invariant
assert(check==true);
return check;
Jbuilder complains about not being able to find the method assert in the class. But it does higlight assert as a keyword i dont get it. What am i doing wrong?

thanks a LOT that did it. It was under Project->Project Properties->general not much difference but to be precise for more newb's in the same predicament.

J2SE 1.4 assertion facility

I'm trying to test drive the new assertion facility in J2SE 1.4 but can't get even a simple example to work:
public class Foo
     public void m1( int value )
          assert 0 <= value;
          System.out.println( "OK" );
     public static void main( String[] args )
          Foo foo = new Foo();
          System.out.print( "foo.m1( 1 ): " );
          foo.m1( 1 );
          System.out.print( "foo.m1( -1 ): " );
          foo.m1( -1 );
Code fails with the following error:
Foo.java:5: Invalid expression statement.
assert 0 <= value;
The compiler fails to recognize the 'assert' keyword - when I change code to:
boolean b = true;
assert b;
the error is:
Foo.java:7: Class assert not found.
assert b;
So, it thinks I'm defining a variable b of type assert rather than recognizing the keyword 'assert'!
I've doing all this in the new J2SE 1.4 - I do have other versions of the JDK on my machine, but am pretty sure I'm compiling against the right one - when I type 'java -version' on command line I get:
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
Anyone any ideas?
Thanks,
Alan

what bs. post-condition type assertions typically
"validate the internal state of the receiver".
pre-condition type assertains are typically used to
validate the state of arguments passed in.
Pre-condition type asserts define the "contract" a
caller must agree to prior to calling. It's very
simple, and very effective.No, you shouldn't use assertions to test pre-conditions. The pre-conditions should always be checked, not just in debug mode. Otherwise, the program could behave differently in debug and release modes, and that would be very undesirable!

Assert is broken

I'm a fairly new Java programmer, coming from a C++ background. Over the past several months, I've written about 26000 lines of Java code, with heavy use of the assert statement to catch bugs and invalid data. Works great. I'm using Borland JBuilder 9, Weblogic edition.
Now that I'm trying to deploy, I've found that assert is broken. You see, in C++ land, assert is useful because it is ignored unless you are in debug mode. Ignored means the compiler ignores it, and the arguments in it aren't evaluated. Won't affect performance.
But now, when I adjust the project settings and uncheck the box that says "enable the assert keyword", I suddenly find my code full of errors: assert isn't ignored, it's just uncompilable!
Hopefully I'm missing something important here. Or is this just broken? Is there a way I can make it ignore (and not evaluate!) the contents of the assert statements? I guess in C++ it's easier, becase assert is a macro. Hmm, maybe this is the reason why it is the way it is: no macros in Java. Am I right?
--- Eric

assert's not broken, it's a flaw either in JBuilder or your understanding.
Why is it that when people have problems they automatically assume that they're doing everything right and the JVM is bugged? I don't get it.
I think you're the problem. Dig deeper - there's a flag in the JVM that will tell the compiler/runtime to ignore the asserts. I just don't know what it is, because I don't use assert. I find that it's always turned off at runtime. During development, I'd rather have a full set of JUnit tests than all the asserts in the world. JMO

"assert" a port range

i am trying to use "assert" more often.
a simple application would be with port ranges:
(1) in unix the max. priviledged port sets the lower
bound of user specifiable ports. but i don't think
this is platform independent?
(2) what is the maximum allowable port number?
i found this: 32767
thanks.

some advice: don't use assert. and, when i say this, i don't mean "don't verify your code", i mean, don't use the assert keyword. the problem comes from the fact that many checks that are asserts should really just be if blocks which throw runtimeexceptions (code that should always be enabled). and, if you have that kind of code using asserts, then you're never going to want to turn them off in production, and then, what's the point in the first place? if you are going to use asserts, i'd recommend only using them in code which is performance intensive (which you know you want turned off in production), and just use normal checks for everything else.
as for your actual question, i think 1024 tends to be a "standard" for the max privileged port number.

Assertion failed: t- numPointers == 0, ....

I develop software on true64 Unix 5.0 and use JDK1.3.1 beta 2 (Fast VM) , I found exception like this
Assertion failed: t->numPointers == 0, file ../../../src/share/native/sun/awt/font/t2k/tsimem.c, line 92
exception system: exiting due to multiple internal errors:
exception dispatch or unwind stuck in infinite loop
exception dispatch or unwind stuck in infinite loop
Had anyone ever met this exception before , what is it wrong , and how can i solve it ?

Hi -
We also came across this problem. It seems to be related to using anti aliased text in a drawString() call. Interestingly it happens on the second call using a particular font.
Test case code is pasted below, which will crash the JVM on the second run through the main loop - i.e. the second time iterating through all the fonts.
This code was cannibalised from another example posted here a while ago.
Chris Davey
===========
import java.awt.*;
import java.awt.font.*;
import java.awt.image.*;
class Test {
public static void main(String[] argv) {
FontMetrics fm = null;
String strings [] ={""," "," ","a","test string"};
int iaBITypes [] = {BufferedImage.TYPE_3BYTE_BGR ,BufferedImage.TYPE_4BYTE_ABGR ,
                            BufferedImage.TYPE_4BYTE_ABGR_PRE ,BufferedImage.TYPE_BYTE_BINARY ,
                            BufferedImage.TYPE_BYTE_GRAY ,BufferedImage.TYPE_BYTE_INDEXED ,
                            BufferedImage.TYPE_INT_ARGB ,BufferedImage.TYPE_INT_ARGB_PRE ,
                            BufferedImage.TYPE_INT_BGR ,BufferedImage.TYPE_INT_RGB ,
                            BufferedImage.TYPE_USHORT_555_RGB ,BufferedImage.TYPE_USHORT_565_RGB ,
                            BufferedImage.TYPE_USHORT_GRAY };
Toolkit t = Toolkit.getDefaultToolkit();
System.out.println("hi");
for (int idx = 0; idx < 100; idx++){
Font fonts [] = GraphicsEnvironment.getLocalGraphicsEnvironment().getAllFonts();
for (int ff=0;ff<fonts.length;ff++) { // Try all fonts
for (int iBIType = 0; iBIType < iaBITypes.length; iBIType++){
BufferedImage bi = new BufferedImage(1000,1000,iaBITypes[iBIType]);
Graphics2D g= (Graphics2D) bi.getGraphics();
//FontRenderContext frc = g.getFontRenderContext();
//XXX Problem Here - if
//2nd Param (anti - aliasing ) is TRUE, then This
//will crash on True 64 Unix - with either Sun or
//Compaq JVM, on 2nd pass through
FontRenderContext frc2 = new FontRenderContext(null,true,false);
//TextLayout tl = new TextLayout("test-string",fonts[ff],frc);
TextLayout tl2 = new TextLayout("test-string",fonts[ff],frc2);
g.setFont(fonts[ff]);
for (float a = -1000; a < 2000; a+=200)
g.drawString("test",a,a);
System.out.println("dumping threads: " );
Thread ath[] = new Thread[512];
Thread.currentThread().enumerate(ath);
for (int i=0; i < ath.length; i++){
if (ath[i] != null)
System.out.println("\tThread: " + i + " " + ath);
Keywords: Tru64 tsimem.c assert true64 crash

Help. Assertion Failed error. LR2

Been using LR2 for a few days. I had just finished keywording a shoot of about 500 images. I then went to the filter bar in grid view to test out the new seach functions. I did a few search combinations then the computer froze. I used task manager to close LR.
When I tried to open LR again I get the message "assertion failed!" with the big yellow triangle with exclamation mark. The catalog is no longer useable and I cannot browse any images at all. I can switch between all modules except library but no image shows up in any of the modules.
Rebooting did not help. I checked integrity of the catalog but did not show anything. I also tried to optimise the catalog. XP SP2.
The software still works using new catalogs. I think I will re-upgrade my old catalog but will work on new images in separate catalogs for now in case this happens again, then merge the catalogs with the main catalog once this issue has been resolved.
Any ideas on how to fix this and recover the work I have done??
Thanks
Kev.

august 21
i got the assertion failed! warning and am at a loss on what to do next. i need help, all the normal reboot/restart stuff has not worked.
the situation when it failed:
i have a multiple large catalogs. the one i was using when this failed has about 45,000 images. i was working on a collection in the develop module, i had just modified an image and was cloning the modifications onto another image (which i had done successfully for the past half hour) and everything stopped and i got the yellow warning triangle with assertion failed! when i went to other modules, i saw may last photo in the print module and on the web module i got "?:0:attempt to index a nil value".
what i've done since then (nothing has worked):
- reboot the pc
- unplugged and replugged the external drive that i was using (WD-2T 1:1, sometimes they seem to overheat and shut down, i had that problem in the past, and just restarting the drive always worked before, but i didn't have the assertion warning then)
- unplugged the drive i had been using and rebooted and started LR again on another drive - LR started but it looks like the catalog is much smaller than it was 2 weeks ago when i upgraded it to LR-2, the files exist on my PC, but i don't see all of them on my catalog.
- retried above with a different large drive and it loaded the LR-2 catalog properly and looks good.
- from the above mentioned LR catalog opened my 'assertion failed' catalog. i got a note that LR needed to check the data base which would take a few minutes. after a few minutes i got the same 'assertion failed' warning note.
any ideas on how to get out of the box? i had just spent the day updating files on this drive along with some printing and organizing.
thanks
john shaffer
[email protected]

Is assert a keyword?

Similar Messages

Maybe you are looking for