Sponsored Content
Top Forums Programming C++ : is what the meaning of #include<stdio.h>? Post 302765997 by neutronscott on Monday 4th of February 2013 03:41:06 AM
Old 02-04-2013
Early in the compiling of a source, a preprocessor takes these # directives. #include basically puts all of stdio.h into the top of your code. the .h identifies it as a "header".

In C, before you use a function, the compiler must first know how it is suppose to be called.

For example, how many arguments and of what type? All this is in stdio.h, for the Standard I/O functions (things that print to the screen and such).

Usually, in C++ it's #include <iostream>, but we won't fault you for using C functions Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

what the meaning of #*

can some one please tell the meaning of the second statement i.e n=${m#*=} i couldnt get the meaning of the #*= 1.) m="mohit=/c/main/issue" echo $m result ----------- mohit=/c/main/issue 2.) n=${m#*=} echo $n RESULT ------- /c/main/issue (1 Reply)
Discussion started by: narang.mohit
1 Replies

2. Shell Programming and Scripting

meaning of !*

can someone please tell what !* means in shell syntax. Regards, (3 Replies)
Discussion started by: busyboy
3 Replies

3. Programming

Atomic Read and Write with stdio

hi guys. can we use fread and fwrite with pipes to write data more than PIPE_BUF atomically since they lock FILE object until I/O operation finish? (1 Reply)
Discussion started by: majid.merkava
1 Replies

4. Programming

stdio.h vs unistd.h I/O

Hi guys. To work with physical files, sockets, pipes, ... which library is good? stdio or unistd stdio.h functions perform buffering and rationally should be better than unistd.h routines. but i am wondering why all UNIX programming books use unistd.h routines for almost all types of I/O... (7 Replies)
Discussion started by: majid.merkava
7 Replies

5. Programming

FILE structure - stdio.h

Hi All, I am new to linux and Programming. Inside the file stdio.h, there is a description about FILE structure. Which has many internal data members like _p, _r, _flags etc. I have written a sample code to find out the contents of the FILE structure. It opens a sample file ( FILE *fp ),... (5 Replies)
Discussion started by: nikunjbadjatya
5 Replies

6. Shell Programming and Scripting

^$$ meaning

Hi , Can anyone please let me know whta the follwoing piece of code for ScriptName=${0##*/} if pgrep -f "$ScriptName" | grep -v "^$$\$" ; then echo `date`": Sctipt $ScritName is already runnig" exit fi Thnx a lot in advance Please use code tags when posting data and code... (8 Replies)
Discussion started by: Pratik4891
8 Replies

7. UNIX for Dummies Questions & Answers

meaning of <<!

Hi all, I wanna know the meaning of the last word "<<! " sudo su - user <<! please help on this !!!! (1 Reply)
Discussion started by: sudharson
1 Replies

8. Programming

stdio.h not found on Solaris 11

Hi friends, I hope u r doing well. I have just installed Solaris 11, and it seems that solaris 11 doesn't come with all the packages, one has to do everything manually. I download gcc from sunfreeware.com and installed it. After setting up the path variable, I tried to compile the hello world... (4 Replies)
Discussion started by: gabam
4 Replies

9. Solaris

fatal error: stdio.h: No such file or directory

Trying to compile a C program recievin this hello.c:1:19: fatal error: stdio.h: No such file or directory gcc is installed on the system. echo $PATH /usr/bin:/usr/sbin:/usr/gcc/4.5/include/c++/4.5.2/tr1 root@Sol11swtb01:/media/NO NAME/Programming/C/Testing# cd... (2 Replies)
Discussion started by: Fingerz
2 Replies

10. Programming

Ignoring the stdio.h file in a C file

I am facing a problem in the below given code. int main() { printf("\nHello Geeks\n\n") ; return 0 ; } In the above mentioned code i left including "#include ". And if i compile and execute this piece of code, the output is printed as expected. But "#include " being the most important... (7 Replies)
Discussion started by: Raj 89
7 Replies
scalac(1)							   USER COMMANDS							 scalac(1)

NAME
scalac - Compiler for the Scala 2 language SYNOPSIS
scalac [ <options> ] <source files> PARAMETERS
<options> Command line options. See OPTIONS below. <source files> One or more source files to be compiled (such as MyClass.scala). OPTIONS
The compiler has a set of standard options that are supported on the current development environment and will be supported in future releases. An additional set of non-standard options are specific to the current virtual machine implementation and are subject to change in the future. Non-standard options begin with -X. Standard Options -g:{none,source,line,vars,notc} "none" generates no debugging info, "source" generates only the source file attribute, "line" generates source and line number information, "vars" generates source, line number and local variable information, "notc" generates all of the above and will not perform tail call optimization. -nowarn Generate no warnings -verbose Output messages about what the compiler is doing -deprecation Indicate whether source should be compiled with deprecation information; defaults to off (accepted values are: on, off, yes and no) Available since Scala version 2.2.1 -unchecked Enable detailed unchecked warnings Non variable type-arguments in type patterns are unchecked since they are eliminated by erasure Available since Scala version 2.3.0 -classpath <path> Specify where to find user class files (on Unix-based systems a colon-separated list of paths, on Windows-based systems, a semi- colon-separate list of paths). This does not override the built-in ("boot") search path. The default class path is the current directory. Setting the CLASSPATH variable or using the -classpath command-line option over- rides that default, so if you want to include the current directory in the search path, you must include "." in the new settings. -sourcepath <path> Specify where to find input source files. -bootclasspath <path> Override location of bootstrap class files (where to find the standard built-in classes, such as "scala.List"). -extdirs <dirs> Override location of installed extensions. -d <directory> Specify where to place generated class files. -encoding <encoding> Specify character encoding used by source files. The default value is platform-specific (Linux: "UTF8", Windows: "Cp1252"). Executing the following code in the Scala interpreter will return the default value on your system: scala> new java.io.InputStreamReader(System.in).getEncoding -target: <target> Specify which backend to use (jvm-1.5,msil). The default value is "jvm-1.5" (was "jvm-1.4" up to Scala version 2.6.1). -print Print program with all Scala-specific features removed -optimise Generates faster bytecode by applying optimisations to the program -explaintypes Explain type errors in more detail. -uniqid Print identifiers with unique names (debugging option). -version Print product version and exit. -help Print a synopsis of standard options. Advanced Options -Xassem <file> Name of the output assembly (only relevant with -target:msil) -Xassem-path <path> List of assemblies referenced by the program (only relevant with -target:msil) -Xcheck-null Emit warning on selection of nullable reference -Xdisable-assertions Generate no assertions and assumptions -Xexperimental enable experimental extensions -Xno-uescape Disable handling of u unicode escapes -Xplug-types Parse but ignore annotations in more locations -Xplugin: <file> Load a plugin from a file -Xplugin-disable: <plugin> Disable a plugin -Xplugin-list Print a synopsis of loaded plugins -Xplugin-opt: <plugin:opt> Pass an option to a plugin -Xplugin-require: <plugin> Abort unless a plugin is available -Xprint: <phases> Print out program after <phases> (see below). -Xprint-pos Print tree positions (as offsets) -Xprint-types Print tree types (debugging option). -Xprompt Display a prompt after each error (debugging option). -Xresident Compiler stays resident, files to compile are read from standard input. -Xshow-class <class> Show class info. -Xshow-object <object> Show object info. -Xshow-phases Print a synopsis of compiler phases. -Xsource-reader <classname> Specify a custom method for reading source files. -Xscript <object> Compile as a script, wrapping the code into object.main(). Compilation Phases initial initializing compiler parse parse source files namer create symbols analyze name and type analysis refcheck reference checking uncurry uncurry function types and applications lambdalift lambda lifter typesasvalues represent types as values addaccessors add accessors for constructor arguments explicitouterclasses make links from inner classes to enclosing one explicit addconstructors add explicit constructor for each class tailcall add tail-calls wholeprog perform whole program analysis addinterfaces add one interface per class expandmixins expand mixins by code copying boxing makes boxing explicit erasure type eraser icode generate icode codegen enable code generation terminal compilation terminated all matches all phases ENVIRONMENT
JAVACMD Specify the java command to be used for running the Scala code. Arguments may be specified as part of the environment variable; spaces, quotation marks, etc., will be passed directly to the shell for expansion. JAVA_HOME Specify JDK/JRE home directory. This directory is used to locate the java command unless JAVACMD variable set. JAVA_OPTS Specify the options to be passed to the java command defined by JAVACMD. With Java 1.5 (or newer) one may for example configure the memory usage of the JVM as follows: JAVA_OPTS="-Xmx512M -Xms16M -Xss16M" With GNU Java one may configure the memory usage of the GIJ as follows: JAVA_OPTS="--mx512m --ms16m" EXAMPLES
Compile a Scala program to the current directory scalac HelloWorld Compile a Scala program to the destination directory classes scalac -d classes HelloWorld.scala Compile a Scala program using a user-defined java command env JAVACMD=/usr/local/bin/cacao scalac -d classes HelloWorld.scala Compile all Scala files found in the source directory src to the destination directory classes scalac -d classes src/*.scala EXIT STATUS
scalac returns a zero exist status if it succeeds to compile the specified input files. Non zero is returned in case of failure. AUTHOR
Written by Martin Odersky and other members of the Scala team. REPORTING BUGS
Report bugs to http://lampsvn.epfl.ch/trac/scala. COPYRIGHT
This is open-source software, available to you under a BSD-like license. See accomponying "copyright" or "LICENSE" file for copying condi- tions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. SEE ALSO
fsc(1), sbaz(1), scala(1), scaladoc(1), scalap(1) version 0.4 April 18, 2007 scalac(1)
All times are GMT -4. The time now is 04:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy