Mubbasher Mukhtar | Sharing Development Experience

Recently I have been looking into a special need to create my own programming language. I have also studied the history of different languages and success and issues they are struggling and stuck with. Here is my personal point of view on this: Creating a Purely new Programming Language The best available language is C\C++ for a cross platform development with different compilers and debuggers. If you are thinking of creating a remarkable new language, HOLD ON,          1- You need to create a compile to target X86, X64, and ARM etc          2- Compiler shall work on Windows, Linux and MAC etc...          3- You need to revisit the entire history of programming language in this case and you have to port all that stuff          4- You Need IDE, compiler          5- Debugger ...

Now in this section, we will create a folder to contain some extra files. 1- How to compile those files. 2- We will create a separate folder to contain the obj files. 3- We will create a separate folder to the output executable as well. Will create a folder called "api" inside the source folder: this folder will contain: mmath.h #ifndef _MMATH_H_ #define _MMATH_H_ double Add(int a, int b); #endif mmath.c #include "mmath.h" double Add(int a, int b) {     return a+b; } Let's update out main as well... main.c #include <stdio.h> #include "api/mmath.h" int main(int argc,char *argv[]) {     double res = Add(23,26);     printf("You see, u see this... I'm running\r\n");     printf("%f\r\n", res);     printf("Externals Executed\r\n");     return 0; } Now How to compile this? We need to include our custom header file as well while compiling and we also need ...

So, let us make our file make file more nice ... Now we will assign symbols, and some targets as well mobi.mk CC=gcc OUT=mobi.exe TARGET=main build:     $(CC)  $(TARGET).o -o $(OUT) compile:     $(CC) -c $(TARGET).c clean:     rm -f *.o $(OUT) now try this nice command... $ make -f ./mobi.mk clean compile build rm -f *.o mobi.exe gcc -c main.c gcc  main.o -o mobi.exe It is better to create a compilation of a module separate when working on it and compile that target only instead of compiling everything... So, for so looks good... Let's add the all target mobi.mk CC=gcc OUT=mobi.exe TARGET=main all: clean compile build build:     $(CC)  $(TARGET).o -o $(OUT) compile:     $(CC) -c $(TARGET).c clean:     rm -f *.o $(OUT) Now, we don't have to specify the targets... $ make -f ./mobi.mk rm -f *.o mobi.exe gcc -c main.c gcc  main.o -o mobi.exe

I kind of hate make files... But let's start it from scratch .... I'll use gcc for the compilation on windows using cygwin ... File name: main.c #include <stdio.h> int main ( int argc , char * argv []) { printf ( "You see, u see this... I'm running" ); return 0 ; } $ gcc main.c -o mobi.exe $ ./mobi.exe You see, u see this... I'm running Great ... Let's make a make file for this. Sounds funny . So, What essentially does a make file do ? It compiles. cool... but helps to keep configuration and order once and for all. file: mobi.mk all:     gcc main.c -o mobi.exe NOTE: Use  notepad for make file... Try not using Notepad++ or u may waste sometime to figure out why. Let use make file: $ make -f ./mobi.mk gcc main.c -o mobi.exe  So for so good...

Suppose we have: List<Car> vCars = new List<Car>(); There are three types of databound controls: Simple databound controls(List, AdRotater), Composite data bound controls(GridView, DetailsView, FormView that inherit from CompositeDataBoundControl), and Hierarchal data bound controls (TreeView, Menu).   DataBoundControl has a DataBind method that can be used when data is ready. It calls DataBind for child controls as well. Page.DataBind() will call DataBind for all child controls. Using DataSource Objects:                                       BaseDataBound control exposes DataSource property that accepts objects that implement IEnumerable , IListSource , IDataSource , or IHierarchalDataSource . DataSourceID accepts ID of SqlDataSource . If both specified Data...